“What is Agile Testing, Anyway?”
Points to remember and Quotable Quotes:
- “Several core practices used by agile teams relate to testing.”
- Programmers using TDD, code integration tests being written contribute to a successful project.
- “Agile Testing just doesn’t mean testing on an agile project.”
- Some testing approaches like exploratory testing are inherently agile, whether done in an agile project or not.
- Testers are integral members of the customer team as well as development team
- The best part of this chapter is Lisa and Janet’s wonderful stories on beginning with their first agile projects, and a realization by Janet’s co-worker, a developer in a team following XP on how they saw Janet’s contribution to the project.
- “Testers don’t sit & wait for work; they get up and look for ways to contribute throughout the development cycle and beyond.”
- Traditional vs Agile Testing
- In Traditional approach – “Testing gets “squished” because coding takes longer than expected, and because teams get into a code-and-fix cycle at the end.
- In Agile – “As an agile team member, you will need to be adaptive to the team’s needs
- “Participants, tests, and tools need to be adaptive.”
- “An Agile team is a wonderful place to be a tester”
- The Whole-Team Approach –
- “Everyone on an agile team gets “test-infected.”
- “An agile team must possess all the skills needed to produce quality code that delivers the features required by the organization.”
- “The whole team approach involves constant collaboration”
- “On an agile team, anyone can ask for and receive help”
- “The fact is, it’s all about quality – and if it’s not, we question whether it’s really an ‘agile’ team.”
Wanna Read along? Get your copy of the book at
OR find a paperback or ebook version!