Added by erik.drolshammer, last edited by Thomas Ferris Nicolaisen on May 30, 2009
()
Strategies and tactics
To web-test or not to web-test
It depends. Remember that even though web-tests may seem easy and quick, they are expensive compared to unit-tests. However, you can get pretty far with just having a single test or script that attempts to do some scraping of your webapp.
Keep them outside the normal build
Cause they're slow.
Choose tools carefully
Depending on the nature of your web application, different tools will suit you. Try out different ones and see what works for you.
Web test tools
| Tool | Type | Opinions and notes |
|---|---|---|
| FITNesse | integrated standalone wiki, and acceptance testing framework | ... |
| Selenium | Web tests | See our Selenium notes |
| Celerity | Web tests | JRuby/Watir wrapper around HTMLUnit, i.e. fast! |
| CubicTest | eclipse plugin for automatic acceptance testing of webapps | ... |
| WebDriver | Web tests |
Headless (these use virtual buffer browsers, like the HttpClient library)
- JWebUnit
- HttpUnit
- Canoo
- Celerity
Browser JS-engine piggybackers
- JSUnit
- Selenium
- Sahi
Native binders (these adapt directly to the browsers)
- Watir/FireWatir
- WebDriver