I use been using Selenium RC [http://seleniumhq.org/] lately. I moved away from QUnit which struggled to be consistent with interaction testing. QUnit was great for testing that function foo returned bar, but it lacked in testing the user interface. Plus you had to manually open up browsers to test.
We hooked up Selenium RC on a virtual machine, and we can test multiple browsers with a click of a button. I know that some developers frown upon testing the user iterface, but interaction testing is a big part in my application since we built widgets based on jQuery UI. Makes it easy to determine if the new version of jQuery or jQuery UI will break my widgets. No more having to manually click hundreds of test pages! It takes 30 minutes to run a full test in multiple browsers which would normally take over a day and a half to do it manually [and hope you did not skip something!] Eric On Sun, Dec 26, 2010 at 8:39 AM, Anton Yacenko <anton.yace...@gmail.com>wrote: > Hi > > There already few replies and will "+1" to jsTestDriver it's best runner on > the market now. > One point regarding tests dependent - it's not a really good idea, the idea > of tests is show how major the problem is, if you break 1 test it most of > all means simple problem, if you broke 1K+ tests - major point. When I've > start use tests I thought like you do it, but reality shows that you don't > need to stop runner on first fail. > > Have a good luck with testing, not much js developers do that and I'm glad > you 1 of us :) > > Anton. > > > On Dec 24, 2010, at 1:28 AM, Glan wrote: > > > Hi All, > > > > I'm interested in getting some people's thoughts on unit testing in > > javascript. I've been looking at qUnit, but an aware of a number other > > methods jsunit,jsspec, jspec etc. With qUnit in particular there are a > > few areas which I'm still unsure about: > > > > 1) Making tests dependent on one another, so if one test fails > > dependent tests are not run. > > 2) Detecting exceptions. If a function throws an exception, how can > > one lookout for this? > > 3) Producing code coverage reports. > > > > Regards, > > Glan > > > > -- > > To view archived discussions from the original JSMentors Mailman list: > http://www.mail-archive.com/jsmentors@jsmentors.com/ > > > > To search via a non-Google archive, visit here: > http://www.mail-archive.com/jsmentors@googlegroups.com/ > > > > To unsubscribe from this group, send email to > > jsmentors+unsubscr...@googlegroups.com<jsmentors%2bunsubscr...@googlegroups.com> > > -- > To view archived discussions from the original JSMentors Mailman list: > http://www.mail-archive.com/jsmentors@jsmentors.com/ > > To search via a non-Google archive, visit here: > http://www.mail-archive.com/jsmentors@googlegroups.com/ > > To unsubscribe from this group, send email to > jsmentors+unsubscr...@googlegroups.com<jsmentors%2bunsubscr...@googlegroups.com> > -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/jsmentors@jsmentors.com/ To search via a non-Google archive, visit here: http://www.mail-archive.com/jsmentors@googlegroups.com/ To unsubscribe from this group, send email to jsmentors+unsubscr...@googlegroups.com
