introduce require.js and rewrite tests

Yes, I'm being lazy. The purpose of require.js is to allow writing
modules, i.e. individual smaller then the whole files with clear
dependencies. This is achieved by using a new api provided by
require.js:

define, require, requirejs

Read more at [requirejs] (http://requirejs.org)

Tests have been rewritten to work correctly with require.js; they still
use jsdom.

Test output is now stored in the repository, all tests are run via
run_tests.js; This is a hack - once a good harness (with assertions,
suites - unittest like) presents itself it will be used.

Hidden here is also using FileSaver for history saving, so history is
saved to history.json instead to a random name. Plus dropping some dead
code.

1 files changed, 31 insertions, 0 deletions

diff --git a/tests/run_tests.js b/tests/run_tests.js
new file mode 100644
index 00000000..bfc129eb
--- /dev/null
+++ b/tests/run_tests.js
@@ -0,0 +1,31 @@
+var fs = require('fs');
+var spawn = require('child_process').spawn;
+
+var tests = fs.readdirSync('.').filter(function (x) { return /^test_.*\.js$/.test(x); });
+var i;
+var testname;
+
+function store_output(proc, args, stdout, stderr)
+{
+    var out = fs.openSync(stdout, 'w+');
+    var err = fs.openSync(stderr, 'w+');
+    var p = spawn(proc, args);
+
+    p.stdout.on('data', function (data) {
+        console.log(args + ' gives ' + data.length);
+        fs.appendFileSync(stdout, data);
+    });
+    p.stderr.on('data', function (data) {
+        console.log(args + ' gives ' + data.length + ' (err)');
+        fs.appendFileSync(stderr, data);
+    });
+    p.on('close', function (code, signal) {
+        console.log(proc + '(' + args.join(', ') + ') exited with ' + code);
+    });
+
+}
+
+for (i in tests) {
+    testname = tests[i];
+    store_output('/usr/bin/node', [__dirname + '/' + testname], 'output/' + testname + '.stdout', 'output/' + testname + '.stderr');
+}