[Cosmo-dev] [Proposal] Use Windmill for JS Unit testing

[Mikeal Rogers]

Can you point us to the current set of jsunit tests and the current  
test runner in the cosmo repository?

I think most of our environment questions could be answered by just  
digging through all that code.

-Mikeal

On Mar 29, 2007, at 9:31 PM, Ted Leung wrote:

> Hi Adam,
>
> The goal here is to have javascript tests for stuff like the  
> backend dashboard plumbing, which don't talk to the UI at all.   
> Real unit tests, in otherwords.  JSUnit gives a JUnit like  
> framework for doing that, but it has to be run manually in a  
> browser, which is annoying for developers who are running  
> everything from a command line or via Maven.  So a solution that  
> makes it possible to run unit tests from the command line and  
> Maven, while using the Javascript engine of one (or all) of our  
> supported browsers would be the goal.
>
> Ted
>
> On Mar 28, 2007, at 3:27 PM, Adam Christian wrote:
>
>> Mikeal and I have a plan to make this kind of testing a lot more  
>> elegant, but it would be really helpful to get peoples  
>> requirements as to how this would be maximally useful. Currently  
>> the tests rely heavily on accessing pieces of the UI to validate  
>> that things are doing what they are supposed to, but it would be  
>> very simple to add some functionality to run js unit tests and  
>> output those results to the windmill ui.
>>
>> Adam
>>
>> On Mar 27, 2007, at 4:55 PM, Ted Leung wrote:
>>
>>> Hi folks,
>>>
>>> So for Cosmo 0.7, we have a bug <https:// 
>>> bugzilla.osafoundation.org/show_bug.cgi?id=5689> for Javascript  
>>> Unit testing.   I did little bit of work on the browser based  
>>> Javascript test runner from JSUnit, and I was intending to work  
>>> on a command-line/maven based build next.   The problem with a  
>>> command line / Maven solution is that the only way to run  
>>> Javascript in those situations is to use something like Rhino,  
>>> which is not the environment where we run our Javascript code.     
>>> In the past we've had Javascript bugs like the Safari date  
>>> problem, which were browser specific, but not related to the DOM  
>>> or other parts of the browser UI.    Now that we have Windmill,  
>>> my current thinking is that we could use Windmill to kick off  
>>> Javascript unit tests that would run in the browser and which  
>>> would use the browser based Javascript runner.
>>>
>>> I'd like to hear people's opinions on whether this is a good idea  
>>> or not.
>>>
>>> Ted
>>> _______________________________________________
>>> cosmo-dev mailing list
>>> cosmo-dev at lists.osafoundation.org
>>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>>
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20070330/f2354b60/PGP.pgp