[Windmill-dev] Tests in native JavaScript

[Matthew Eernisse]

Good stuff, reeponses below.

Mikeal Rogers wrote:
> It's kind of hard to explain the current workflow for tests in windmill 
> and how this is a departure and will have to be special cased, but I'm 
> going to try because I don't think my replies below will make sense 
> without it.

Thanks for explaining this. I had a vague idea of the 'lifecycle' of a 
test, but this makes it all much more concrete.

> Say we didn't bundle the javascript test writing work with the JSUnit 
> work. We would then need to write up an entirely new testing framework 
> in javascript for it and we would need to duplicate the effort of 
> creating a reporting mechanism in windmill for tests that don't come 
> through the service.

The overlap seems to be in the need for a reporting mechanism for tests 
that aren't passed over from the service. And obviously the native JS 
tests for Windmill require extra work to define an API.

Is the work required for JSUnit integration simply a prerequisite for 
native JS tests -- or is there extra work that would be needed 
specifically for the Cosmo JSUnit tests? If there's no extra work, then 
yeah, it makes sense to knock it all out in one fell swoop.

Otherwise, if there are discussions for the JSUnit work that could drag 
on for awhile, I'd really like to lay the groundwork first, and then do 
the work for JS tests and JSUnit integration on separate tracks.


Matthew