[Windmill-dev] Windmill 0.4 Roundup

[Mikeal Rogers]

> Not sure how you'd write unit tests for filter/phase limiting, as  
> they're attributes of the *test run*, not anything in the tests  
> themselves. Their value is during dev and debugging, not during  
> actual testing. Anybody have any ideas how we could do tests for that?

We do need to work out the semantic for you informing the backend of  
your whole test run status at the end of the test run.

The results object you give to the backend will have the list of tests  
run.

I'll be creating an XMLRPC method for executing the js framework. We  
can call that with various filter/phase limiting and check the test  
run result objects in pure Python.

For now tho, we need unittests for all the jsTest methods, just like  
we have the vanilla windmill API. For now we can just focus on tests  
that return true, we can work out a way to test failures and waits  
later using something along the lines of what i outlined for the  
filter/phase limiting.

We don't need 100% of the features covering in unittests before we  
release, i just want the first run of them in and we can improve/ 
expand them later. As it stands we have zero, we definitely need more  
than zero before we release.

>
>
> I think Adam would be the one to ask about calling new methods on  
> test-run completion. Adam, any clue about that?

Whoever wrote the code that calls report_without_resolve() would be  
the most likely person to do this work as well, whoever that is.

-Mikeal