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

[Matthew Eernisse]

That all looks kosher to me. It would be super-cool to get this 
implemented so we can do more with the JS tests. I've got the 
auto-parsing and setup/teardown, seems like this is all that's left.

I didn't know there was a UUID for the test run. Should we be doing 
something with that in the JS tests? Or are we, and I just don't know it?


M.

Mikeal Rogers wrote:
> Ok, here is how I think things will work on my end.
> 
> $ windmill jsdir=test_js jsfilter=ns:blah
> 
> or
> 
> $ windmill jsdir=test_js jsfilter=method:blah
> 
> The jsdir is mounted and recursively parsed for .js files, the filter 
> and all the .js urls are sent in a single callback to the IDE along with 
> a UUID for the test run.
> 
> {
> 'method':'commands.jsTest',
> 'params':{'files': [ ---list of urls---],
>                  'filter': "ns:blah",
>                  'uuid': "sadf-asdf-asdf-asdf-asdf" }
> }
> 
> If it makes things easier, we can rename the uuid option as to not 
> confuse that uuid param to the root level uuid param for all RPC calls 
> between the Service and IDE.
> 
> Thoughts?
> 
> -Mikeal
> _______________________________________________
> Windmill-dev mailing list
> Windmill-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/windmill-dev
>