Quality Is Job #1
The testing approach I've described here is different from the traditional, documentation-heavy approach where you throw the system and its specifications over the wall to testers and hope for the best. My experience is that the quality of your system is only as good as the quality of your testing efforts.
Thanks to Michael Bolton, Cem Kaner, Renu L. Rajani, and Steve Robinson for their insightful feedback.
|
Agile Testing Resources
You should find the following resources full of provocative ideas about how to improve your testing efforts:
• Agile Testing Mailing List (tech.groups.yahoo.com/group/ agile-testing).
• Context-Driven Software Testing Mailing List (tech.groups.yahoo .com/group/software-testing).
• "High-Volume Test Automation," by C. Kaner, W.P. Bond, and P. McGee (www.kaner.com/pdfs/HVAT_STAR.pdf).
• James Bach's blog (www.satisfice.com/blog).
• "Lessons Learned in Software Testing," by C. Kaner, J. Bach, and B. Pettichord (www.testinglessons.com).
• Michael Bolton's testing articles (www.developsense.com/articles).
• "Roadmap for Agile Testing" and "The Testing Team's Motto," by Brian Marick (www.testing.com/writings).
• "What Is Exploratory Testing?" by James Bach (www.satisfice.com/articles/what_is_et.shtml). |
