[Windmill-dev] js framework "exit on done" work
mikeal at osafoundation.org
Mon Oct 22 19:14:29 PDT 2007
I don't know what these methods mean?
js_test_run_final is a special case to tell the service that the
jsTest framework is complete so a framework can query the Service and
get state in order to move along or kill the browser.
I don't understand what test_run_final is suppose to be, and if it's
a service method I don't know what it's use is or who calls it, if
it's a shell method I'm equally confused. Not being camelCase I'm
assuming it's not a callback that is handed off to the IDE.
Very very confused.
On Oct 22, 2007, at 7:06 PM, Adam Christian wrote:
> So if I wanted to run the whole suite of ide tests and i didn't
> want a suite to be just a single file, we may want to following:
> That way when any set of tests starts and finishes we know that and
> can notify the user accordingly.
> On Oct 22, 2007, at 6:46 PM, Matthew Eernisse wrote:
>> I actually remember asking about this before -- it's a pretty
>> standard thing to want to know when an entire suite has finished.
>> Of course that would require that we have some kind of a larger
>> concept of a 'suite.'
>> But it would be nice to be able to call a big blob of tests, and
>> then get some kind of summary when the entire thing is done.
>> Adam Christian wrote:
>>> This sounds fine to me, I was also thinking that this might not
>>> be such a bad idea for the non js tests.. that way the IDE can
>>> actually display some output like.. "Suite finished running" etc
>>> so people don't have to guess on the state.. ideas?
>>> On Oct 22, 2007, at 2:50 PM, Mikeal Rogers wrote:
>>>> Trying to get the js based tests hooked up I just noticed some
>>>> 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
>>>> 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
>>>> to be notified of?
>>>> Windmill-dev mailing list
>>>> Windmill-dev at osafoundation.org
>>> Windmill-dev mailing list
>>> Windmill-dev at osafoundation.org
>> Windmill-dev mailing list
>> Windmill-dev at osafoundation.org
> Windmill-dev mailing list
> Windmill-dev at osafoundation.org
More information about the Windmill-dev