440 likes | 990 Views
08/12/2011 migle@adform.com. Agile Testing. Agenda. Challenges in Agile testing “Must’s” of Agile testing Testing as a team Path to Agile testing Going the path Measuring traveled distance. Challenges. C1. Fast feedback. C2. No documentation. C3. Old practices are inefficient. C4.
E N D
08/12/2011 migle@adform.com Agile Testing
Agenda Challenges in Agile testing “Must’s” of Agile testing Testing as a team Path to Agile testing Going the path Measuring traveled distance
Challenges C1 Fast feedback C2 No documentation C3 Old practices are inefficient C4 Sprint start/end problems C5 Agile way of quality C6 No metrics C7 Lots of regression
Testing against documentation Good testing Good documentation Quality
Testing against documentation information Product owners User manuals Developers Existing product Good testing Good documentation Quality
Regression eats time Feature testing Feature regression testing
Regression eats features Development Packet creation Regression Development Development Packet creation Regression
New team member - robot A1 Unit tests A2 Automated regression
Quickwins Manual Automated
Quickwins Manual Automated
Quickwins Manual Automated
Quickwins Manual Automated
Exploratory testing Scripted testing Exploratory testing Ad hoc testing
Exploratory testing Step 1 Plan testing activities Step 2 Execute tests React and adapt Step 3 Make regression test cases
The Must’s M1 Automate regression M2 Use traditional practices if needed M3 Exploratory testing – main way ofmanual testing M4 Test as a team M5 Risk/priority based testing M6 Code review / pair programming M7 Continuous integration
Being agile – being part of the team Developer Tester Team
Agile tester R1 Plan / take metrics in the beginning of sprint R2 Learn from / helpwith unit tests R3 Execute manual testingandregression R4 Make regression test cases R5 Drive testing process R6 Constantly gather information R7 Maintain test cases R8 Execute pair testing / pair programming
Agile programmer developer R1 Create unit tests R2 Automate regression tests R3 Execute manual regression R4 Code review / pair programming
Scrum master R1 Use influence to get regression automation R2 Provide balance
Product owner R1 Review regression test cases R2 Provide information about priorities / risks
Path to Agile testing S1 Empower people S2 Automate regression S3 Start practicing traditional practices S4 Start practicing exploratory testing S5 Start reading unit tests. Pair programming /pair testing S6 Optimize. Be Agile
Going the path Each team at own phase Learning from leaders Common process and tools Measure and adopt Testers knowledge sharing
“You can’t control what you can't measure.” Tom DeMarco
Measuring traveled distance TM1 Test success rating TM2 Code coverage % TM3 Test automation % BM1 Defects – fixes ratio
References www.testingexperience.com/testingexperience03_09.pdf http://www.agiletesting.info/ http://www.ambysoft.com/essays/agileTesting.html http://www.scrumalliance.org/articles/392-agile-testing-key-points-for-unlearning http://www.testertroubles.com/ http://www.google.com