Monday, November 28th, 2005p>Joseph Moore recently wrote about how his team is working with Selenium to test their ajax apps. Most of the normal Selenium actions weren’t working well for the ajax calls, as they are expecting synchronous communication.
So Joseph used the “waitForValue” and “waitForCondition” features, which can just sit and watch for the DOM or input values to change after the async call was made. He says:
Why the Selenium folks don’t have bright red “hey, use this for your Ajax testing!” flag on these two items is beyond me.
Right now it seems there are so many different approaches to testing Ajax that developers aren’t sure where to start. There isn’t a clear cut framework or approach that has the dominance of the xUnit approach for the server side code.
Further resources to muddy the waters =) :
- System testing at AjaxPatterns
- Browser-side Test at AjaxPatterns
- Ajaxian’s previous coverage of Selenium
- Dojo’s wiki page on writing unit tests
- Watir: Web App Testing in Ruby
Posted by Rob Sanheim at 12:39 am