The Agile Tester’s Mindset

Download The Agile Tester’s Mindset

Post on 11-May-2015




2 download

Embed Size (px)


On traditional projects, testers usually join the project after coding has startedor even later when coding is almost finished. Testers have no role in advising the project team early regarding quality issues but focus only on finding defects. They become accustomed to this style of working and adjust their mental processes accordingly. On agile projects, where testers must collaborate closely with customers and programmers throughout the development lifecycle, their focus changes from finding defects to preventing them. Janet Gregory shares ways to change the testers mindset from How can I break the software? to How can I help deliver excellent software?a critical mental shift on agile projects. Another aspect of the mindset change is learning how to test early and incrementally. Janet uses examples to help you understand how effective this mindset change isand how you can apply it on your agile projects.


  • 1. AW8 Session 6/5/20132:15PM "The Mindset Change for the Agile Tester" Presented by: Janet Gregory DragonFire, Inc. Broughttoyouby: 340CorporateWay,Suite300,OrangePark,FL32073

2. Janet Gregory DragonFire, Inc.Agile testing coach and practitioner Janet Gregory (@janetgregoryca) is the coauthor of Agile Testing: A Practical Guide for Testers and Agile Teams and a contributor to 97 Things Every Programmer Should Know. Janet specializes in showing agile teams how testers can add value in areas beyond critiquing the product. For the past ten years, she has been working with teams to transition to agile development. Janet teaches agile testing courses and tutorials worldwide, contributes articles to leading publications, and enjoys sharing her experiences at conferences and user group meetings worldwide. Find more information at or visit herblog. 3. 5/1/2013June 2013 Agile Development Conference West Janet Gregory, DragonFire Inc. Copyright 2013First agile team 2000 Currently coaching, testing Book Agile Testing; January 2009 Copyright 2013 DragonFire Inc.21 4. 5/1/2013 Test more than just code Testing is an activity; not a phaseCopyright 2013 DragonFire Inc.2 5. 5/1/2013Analytical Relentlessly Curious Observant Skeptical Empiricist Critical Thinker InvestigatorDisciplinary skillsCross-functional knowledge Copyright 2013 DragonFire Inc.Instead of Were here to find bugs or ensure requirements are met or break the software Think What can I do to help deliver the software successfully!Copyright 2013 DragonFire Inc.63 6. 5/1/2013 Collaboration means ... Working together to find solutions, etc. The whole team .. Customers, testers and programmers .. Communication means ... sharing Ideas, information, decisions, solutions, etc.Copyright 2013 DragonFire Inc.4 7. 5/1/2013Iteration levelStory test levelSystem levelRelease level Understand the business needs What level are at? Collaborate appropriatelyTask level Copyright 2013 DragonFire Inc. Power of Three 3 Amigos Pairing Continuous feedbackCopyright 2013 DragonFire Inc.105 8. 5/1/2013Explore examplesUser Story Accept StoryHigh level AT Fix defectsExploreExpand TestsExploratory TestingCode & Execute testsAutomate testsCopyright 2013 DragonFire Inc.11 Examples provide common language Shared common understanding Coding and testing concurrently Involves whole team Shared definition of DONE Prevents defectsCopyright 2013 DragonFire Inc.126 9. 5/1/2013Checking: Confirmation Machine decidableGUIAPIUnit TestsTesting: Exploration & learning Requires sapience **Definitions of testing vs. checking by Michael Bolton Copyright 2013 DragonFire Inc.147 10. 5/1/201315168 11. 5/1/2013Its not just about code !!! Test assumptions Uncover hidden assumptionsThe goal: Shared common understanding of the story Preventing defects (eliminate waste)Copyright 2013 DragonFire Inc.9 12. 5/1/2013 Know your context Have a tool box full Simple is often best Use your imaginationLets look at some examplesCopyright 2013 DragonFire Inc.Words / Phrases I wonder . What caught your attention? Could you show me? What makes you think there is more?Questions / Predictions What might happen next? Why would that be? What is the worst thing that could happen? . or the best? What assumptions do you have?10 13. 5/1/2013 Practice anticipating what will happen Define your tests Check running tests or collaborate with customers and programmers before* coding Be prepared to change your tests if your predictions are wrong Learn by reviewing what questions could you have asked first. Copyright 2013 DragonFire Inc.21rules Sub topicrulesuser namesavepassword Sub topicfirst time Sub topicencryption MAIN new account TOPICSub topic change Sub topicLogin : User name & password11 14. 5/1/2013Copyright 2013 DragonFire Inc.232412 15. 5/1/2013 Think simple Have a variety of tools Adapt to your needs Look in places you may not have consideredCopyright 2013 DragonFire Inc.13 16. 5/1/2013 Curiosity Ability to observe Ability to challenge Ability to adapt To recognize contexts Technical awareness Ability to THINK !Copyright 2013 DragonFire Inc.Challenge Yourself ! 2814 17. 5/1/2013Agile Testing: A Practical Guide for Testers and Agile Teams By Lisa Crispin and Janet Gregory www.agiletester.caContact info Email: Twitter: janetgregorycaCopyright 2013 DragonFire Inc.29 Elisabeth Hendrickson CAST keynote Explore It! new book on Pragmatic Programmers Ben Kelly, Markus Gartner, Paul Carvalho, Michael Bolton, Ready to Use Graphic Organizers15 18. 5/1/2013 - Brian Maricks web site Gojko Adzic, Bridging the Communication Gap, 2009; Specification by Example, 2011 Pragmatic Personas - Jeff Pattons weekly column 1/25/2010 Jean Tabaka, Collaboration Explained, 2006 Addison-Wesley Portia Tung Power of Play Ester Derby and Dianne Larsen, Agile RetrospectivesQuestions?Copyright 2013 DragonFire m16