On 12/22/10, Eric Pascarello <[email protected]> wrote: > What is different about your framework than the others that are out there? > > http://seleniumhq.org/
Totally different animal. Selenium's for acceptance testing. I used that before for a company where the "customer" was the business folks. Was a great way to show new features. Very impressive that you can have selenium to launch the browser and run the app as a user would. When I was at that company, I wrote a number of their tests in Java (the commands are translated to "Selenese"). The tests define what the app does. Documentation? Run the test. When a bug or unusual path is found, it can be addressed, tested, and, as with any testing, it is up to the developer to ensure that the other tests still pass. It's a bit of work and RTM to get Selenium Grid set up. You'll also need to get others on the team to agree on the logistics of when the acceptance meeting (presentation to customer) takes place (though usually it occurs at the end of a sprint). Selenium was my inspiration for "waitForCondition", BTW. > http://www.jsunit.net/ Unit testing. Some pitfalls: Uses frames and when it doesn't load or loads a different file, it can make you feel dumb for not referencing the right file ("oh crap I did it again"). Does not have async features such as "wait" or "waitForCondition" No DOM event synth. Decent stack trace though -- possibly worth stealing. > http://docs.jquery.com/Qunit > Dunno about that one. Got influence from YUI Test, too. Filed a ton of bugs on it, too, at the author's request. I ended up with my own patched version and AFAIK, none of those bugs have been fixed, many of those bugs from early 2008. I also submitted a full patch for Apple Touch Events eventsynth, put it on github, linked to the patch Well, I can just use those in domunit now. DOMUnit's less plumbing and uses small functions which makes debugging a lot easier "step over" a 5 function calls is a lot easier than stepping over 100 statements. And all you need do is call runTests(). Web based unit testing is a little different than unit tests for say, Java. It involves, closures, the DOM, user driven events, and browsers. -- Garrett -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
