--- !ditz.rubyforge.org,2008-03-06/issue title: add an include mechanism to test cases desc: |- Also go through test cases to find common helpers and make utils out of them. Naming could be something like 'util-checksum-string.js'. type: :task component: duk release: v0.10 reporter: sva status: :unstarted disposition: creation_time: 2013-03-04 21:37:35.146280 Z references: [] id: 6bb11f83617767ce219e5491239cf1502d61c0cc log_events: - - 2013-03-04 21:37:35.319304 Z - sva - created - "" - - 2013-03-28 21:43:27.745589 Z - sva - assigned to release v0.5 from v0.4 - "" - - 2013-04-21 19:31:48.647890 Z - sva - assigned to release v0.6 from v0.5 - "" - - 2013-08-02 14:54:00.297929 Z - sva - assigned to release v0.7 from v0.6 - "" - - 2013-09-29 10:01:18.754438 Z - sva - assigned to release v0.8 from v0.7 - "" - - 2013-10-31 00:12:36.979476 Z - sva - assigned to release v0.9 from v0.8 - "" - - 2014-01-12 13:33:37.343951 Z - sva - assigned to release v0.10 from v0.9 - "" - - 2014-01-13 23:14:42.259612 Z - sva - assigned to release v0.9 from v0.10 - "" - - 2014-01-15 22:34:39.081780 Z - sva - commented - |- The include mechanism should probably be the module mechanism. This would make test cases still runnable from command line as long as there is a compatible module mechanism. - - 2014-01-16 21:33:05.445952 Z - sva - assigned to release v0.10 from v0.9 - "" - - 2014-01-17 20:22:12.908793 Z - sva - commented - |- Ecma-262 has a model where a testcase is "prepped". This might work quite well also for Duktape testcases. Test cases which are "raw" and test for basic parsing of functions etc don't need the same prepping, but this can prevented in test case metadata.