Hey all, On the topic of automated unit testing, here's an email from the Opencast list with some documentation on how they have used JSTestDriver.
TestSwarm is probably a better long-term option, but these links should provide us with some real-world background information. Colin Begin forwarded message: > From: Markus Ketterl <[email protected]> > Date: March 3, 2010 8:51:11 AM EST > To: Opencast Matterhorn <[email protected]> > Subject: [Opencast Matterhorn] UI testing cookbook sections > Reply-To: Opencast Matterhorn <[email protected]> > > Hi frontend developers, > i´ve added ui testing sections to our Matterhorn Cookbook to be prepared for > iteration 10. > > There you will find. > > Javascript unit testing: > http://opencast.jira.com/wiki/display/MH/JavaScript+Unit+testing > > Running QUnit in a java based module: > http://opencast.jira.com/wiki/display/MH/Integrate+javascript+tests+in+the+build+process+-+second+approach > > Running javascript tests in multiple browsers, create code coverage reports > for your code, maven integration: > http://opencast.jira.com/wiki/display/MH/Integrate+javascript+tests+in+the+build+process > > Improving your code quality / creating code documentation > http://opencast.jira.com/wiki/display/MH/Tools+and+examples+to+improve+the+quality+for+non-java+development > > > Let me know if you have further questions or ideas. > > Markus > > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ --- Colin Clark Technical Lead, Fluid Project http://fluidproject.org _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
