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

[Mikeal Rogers]

I'm trying to think about this more from the user using the windmill  
command line to call this stuff.

To me, I think having three options for JavaScript tests that all  
relate to each other is a bit much. That's why I wanted to keep it all  
in the filter= option.

If you're concerned about the callback semantics I can do what you're  
saying below without any problem, but I think you are also making a  
statement about how you would like the command line options to work.

I'm at a loss here. I think my head is too far in to how this  
particular set of functionality is implemented between the Service and  
IDE to think of what we should be presenting the user.

I'm open to any suggestions. For the rest of this thread can we talk  
about both the public facing part of this (windmill command line  
options and shell commands) and the backend callback implementation  
and how they relate so that we don't get confused or make assumptions  
about the others opinion.

Anyway, I'm ready to listen to suggestions because I just can't  
separate myself from the implementation enough to have a strong  
opinion about the user experience.

-Mikeal

On Dec 19, 2007, at December 19, 20073:51 PM, Matthew Eernisse wrote:

> Responses below ...
>
> Mikeal Rogers wrote:
>> Good point, could we use the filter option for that?
>> filter=only:setup
>>          only:setup/teardown
>>          only:test,ns:blah
>
> It might make more sense to keep the two concepts separate.
>
> The "filter" indicates *which tests* to run.
>
> I think need another option ("only"?) to indicate *which steps in  
> the test cycle* to run.
>
> {
> 'method': 'commands.jsTest',
>  'params': { 'filter': 'ns:test_pim.test_unsavedChanges',
>    'only': 'setup,test',
>    'uuid': 'foo-bar-baz-blammo' }
> }
>
> If the "only" option is omitted, it just runs setup, test, teardown,  
> like normal.
>
> Does that make sense? I think it might be a little easier for end- 
> users than overloading filter.
>
>
> Matthew
>
> _______________________________________________
> Windmill-dev mailing list
> Windmill-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/windmill-dev