…is used as a pipe and kept open.
…d events on a remote host; and server-client-comm, which is invoked on the coordinating host in order to communicate with clients. Updated handling of command line args in harness coordinator module Updated browser-main to fix sending of updated configurations so that they are sent sequentially.
…s. This should make it easier to probe failed tests.
…Seems to work with one client; next step will be to test on multiple clients.
…fb as alternative to Xephyr for x server.
…ronment were set incorrectly, causing infinite recursion.
…optimization was not being initialized correctly, causing some tests to fail. Fixed the browser-main runner, as it was clearing the buffer too late, which was also causing some tests (e.g. TestInPredicate) to fail.
…tool.focus was being called before sending keyboard event, which was causing events to not be received by the browser window, failing intermittently. Next step will be to try to run all tests.
…ome tests are failing unexpectedly, which needs to be investigated.
… simple test. Next step will be to run all tests.
Also, broke out defaultTransitionSelector into its own module.
…ierarchical lookups. All tests pass.
Implemented ahead-of-time, transformational optimization: transition flattening. Added flattenTransitions.xsl to implement this transformation. Integrated flattening of test cases into build and test infrastructure. This exposed a bug in the interpretation algorithm (e.g. for an example of this bug, see the transition-flattened version of parallel+interrupt/test19.scxml). Fixed the bug in the interpreter in a slightly clever way, checking each state's selected transitions for consistency, before comparing all selected transitions for consistency. Decided that convention over configuration would be better in the naming of test scripts, so updated all JSON test scripts to remove redundant information: test name, group, and location of associated SCXML file. All tests, both flattened and non-flattened, with all optimizations pass under rhino and node.
…cestors, descendants, state depth, and transition LCA), and caches it in the model used at runtime. This will potentially speed up stachechart execution.
…d on positional arguments), which I think is much cleaner.
…t testing harness. Passes all tests under both node and rhino.
…object, as state order is important in many optimizations.
…ts pass for all transition-select optimizations and non-optimized executions under node and rhino. Next step is to implement and test other optimizations.
…make, and less like Ant.
…ition selection. Just finished the modules that will generate code for this. Next step is to integrate and test it.
…datamodel returned by scxmlToJSON. There was too much redundancy in the having two models. Having one model should make it easier to implement many of the ahead-of-time optimizations.
…. Created launcher scripts for starting test harnesses for node and spartan shell. Integrated with Makefile. Moved some duplicate code from test harnesses out into their own models. Generalized runner.js so that it could also be used when running under node.
…es, to be used for running tests in spartan shells.
… under spartan js shell environments using RequireJS.
…t shells that only expose load() and print() functions. Can be found in my requirejs fork on github.