[Cosmo-dev] [Proposal] Use Windmill for JS Unit testing
mikeal at osafoundation.org
Fri Apr 6 00:56:25 PDT 2007
To clarify, bobby wants jsunit tests to be written independent of the
framework they run in.
We can run the tests in windmill or if someone wanted to run them in
the standard jsunit framework they could.
Sometime next week Adam and I will work on a proposal.
On Apr 5, 2007, at 1:28 PM, Adam Christian wrote:
> So I'm a little confused as to how I am supposed to make JS Unit
> testing happen with Windmill, without having Windmill as a
> requirement.. could someone enlighten me?
> The only thing I can come up is having the JS Unit test runner talk
> to the windmill server as an option, otherwise output to std out
> but that still leaves us the problem of how are we actually running
> the tests. I can easily add functionality to windmill to pass in
> that result and send it to the server, but the requirements here
> are a little vague.
> On Mar 31, 2007, at 10:10 AM, Bobby Rullo wrote:
>> Please just keep in mind that making sure the tests run without
>> windmill is a requirement.
>> On Mar 31, 2007, at 2:13 AM, Mikeal Rogers wrote:
>>>>> If we can find a way to dynamically replace the regular jsunit
>>>>> assertion methods with our own I think we can do this all
>>>>> pretty easily.
>>>> I still don't see the reason for this...Could you explain?
>>> Since windmill will be responsible for running tests and
>>> gathering results we'll need to override the validation methods
>>> to call pass/fail in our own windmill jsunit test framework. I'm
>>> sure we could find a way to hook into the jsunit module and
>>> gather the results after running, but bending everything to run
>>> in windmill will be more difficult than just replacing the
>>> validation functions dynamically.
>>>> Well js is one of them thar dynamical language things, so it
>>>> ought to be possible. Should I reassign the jsunit related bug
>>>> (s) to you or to Adam?
>>> sent back to the windmill server over jsonrpc and at some point
>>> I'll be responsible for printing and logging them, but for the
>>> most part this is Adam's works and all bugs should be assigned to
>> cosmo-dev mailing list
>> cosmo-dev at lists.osafoundation.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20070406/5f4b8471/PGP.pgp
More information about the cosmo-dev