James Lyndsay - Testing in an agile environment
1 like559 views
The document discusses testing in an agile environment. It begins by outlining the values of agile software development according to the Agile Manifesto, prioritizing individuals and interactions, working software, customer collaboration, and responding to change over processes/tools, documentation, contract negotiation, and following a plan, respectively. It then discusses that in an agile environment, testing is automatic through comprehensive testing via refactoring and continuous integration. Errors should be avoided through practices like metaphor, pair programming, 40-hour work weeks, and coding standards. Friction is reduced through improved communication using techniques like planning games, small releases, simple design, collective ownership, and on-site customers. The document concludes
James Lyndsay - Testing in an agile environment
- 1. Testing in an agile environment James Lyndsay, Workroom Productions Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com Agility (agility) Manifesto for Agile Software Development Kent Beck Mike Beedle Arie van Bennekum We are uncovering better ways of developing Alistair Cockburn software by doing it and helping others do it. Ward Cunningham Through this work we have come to value: Martin Fowler James Grenning Jim Highsmith Individuals and interactions over processes and tools Andrew Hunt Ron Jeffries Working software over comprehensive documentation Jon Kern Brian Marick Customer collaboration over contract negotiation Robert C. Martin Steve Mellor Responding to change over following a plan Ken Schwaber Jeff Sutherland That is, while there is value in the items on Dave Thomas the right, we value the items on the left more. © 2001, the above authors this declaration may be freely copied in any form, but only in its entirety through this notice. Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com
- 2. Working software is preferable to comprehensive documentation Individuals and interactions are preferable to processes and tools
- 3. Customer collaboration is preferable to contract negotiation Responding to change is preferable to following a plan
- 4. My conclusions Challenge your beliefs: the virtues of independent testing the importance of documentation the necessity of long-term planning Bring your skills, and work within the team Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com Agility (agility) Testing is Automatic Errors should be Avoided Friction is reduced by Improved Communication Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com
- 5. Testing is Automatic Comprehensive testing, but not by testers Refactoring Continuous integration Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com Errors should be Avoided Metaphor Pair work 40-hour week Coding standard Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com
- 6. Friction is reduced by Improved Communication Planning game Small releases Simple design Collective ownership On-site customer Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com Old or new? Style or Substance?
- 7. My experiences Tester – reported bugs Participant – part of the agile team Mentor – to a test lead on an agile project Consultant – after implementation problems Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com Bugs missed, lessons learned You can’t get the bugs out of Microsoft Word even automated unit test have their limits The side-effects of unexpected truncation Test driven design? No test = no code Discounts that don’t It’s easy to get used to a bad behaviour Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com
- 8. What’s it like? You’ll talk to everyone, and get involved in their testing You’ll occasionally fix a bug You’ll lose your independence You learn to live without (some) documentation Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com Common problems Testing in later iterations Keeping testing and coding in sync Test management Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com
- 9. Common problems Passing tests ! working code Agile ! Exploratory Testers can make a terrible mess Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com Testers help Bring your own stories and skills Expose and diagnose the unexpected Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com
- 10. Exploration and diagnosis Necessary Similar spirit Not a perfect fit Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com Supporting the learning process Give fast feedback Enhance the work of the team Be involved in retrospectives Re-factor required processes Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com
- 11. Exploratory Testing Seminar 31 July, Dublin Through Insight www.insight-test.com ... or see workroom-productions.com Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com jdl@workroom-productions.com AIM/Skype: workroomprds
- 12. I mentioned the following resources: Paper at www.workroom-productions.com/papers.html Beck: eXtreme Programming Explained Yahoo Groups: aa-ftt, agile testing Variations on this talk will be delivered at Agile2008, EuroStar Testing in an Agile Environment © Workroom Productions 2008 SoftTest June 2008 www.workroom-productions.com