[Windmill-dev] js framework "exit on done" work

[Mikeal Rogers]

Trying to get the js based tests hooked up I just noticed some problems.

1) The Service has no idea when the jstests are finished. I can guess  
by waiting for the IDE to call next_action() but this is problematic.
2) If we just add a simple "I'm done" method to the Service it then  
has no way to differentiate between multiple js test runs.

What I propose is to make some additions to both interfaces.

Currently commands.jsTests only takes one argument, "tests" which is  
a list of the js files it's recursively parsed from the given  
directory. I'd like it to take another argument, "uuid" which will be  
a standard UUID for the test run.

At the end of that test run, the js framework should call a new  
method in the Service called "js_test_run_final" with params "uuid"  
and "results" (a serialized list of the test results -- i believe  
you're already keeping this somewhere).

This way the Service can make multiple test runs and people can query  
the server to see the status of any test run. This work can also be  
leveraged once we go multi-client with minimal changes.

The Service will be implementing additional methods so that remote  
xml/json-rpc clients can start js test runs and get the results from  
the Service.

If anyone else would like to add more methods or options to the js  
test workflow now would be a good time. Is there anything else going  
on over in JavaScript land that the Service might was to be notified of?

-Mikeal