[Windmill-dev] JS test suite or test setup/teardown

[Mikeal Rogers]

> (Namespace, run setup & test)
>
> filter=ns:test_pim.test_unsavedChanges, phase=setup,test
>
> (Single-test, run test only)
>
> filter=test_pim.test_unsavedChanges.test_clickLozengeDiscard \
> phase=test
>
> I think I like 'phase' better than 'only' -- it's clearer, and more  
> descriptive.
>
> Hope that makes sense.

Ok, i think we are agreed that we need two commands. But this naming  
isn't going to work, these options are global windmill options that  
are specific to the JavaScript framework so they need to be prefaced  
with something. Here are some ideas.

jsdir=root directory of your js tests to be mounted, parsed, and send  
to the framework

jsfilter=filtering for the test framework, supports  
ns:string_match_filter and tests:string_match_filter

I don't like the work "phase", it's not specific enough, because what  
it actually means is "run only this phase". I would prefer

jsrunonly=setup,teardown # I think we do need it command delimited,  
because I can see a need for running jsrunonly=setup,test very often.

or

jsonlyrun=

To move on to some of the semantics here, when the jsdir option is  
present the backend assumes the FIRST thing it should do is run the js  
test framework. Any other test running options sent to windmill will  
be executed in a callback _after_ the jstests are finished.

Important question; Will the IDE ever call next_action() between being  
handed the JavaScript framework execution callback and it finishing  
running those tests?

-Mikeal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/windmill-dev/attachments/20071220/d0faafcd/attachment.htm