Agile Testing Practices Good Food for all Teams

Size: px

Start display at page:

Download "Agile Testing Practices Good Food for all Teams"

Oscar Powers
5 years ago
Views:

Agile Testing Practices Good Food for all Teams www.

1 Agile Testing Practices Good Food for all Teams 1 January 30, 2007

2 Abstract Agile testing practices have evolved in part as a response to short duration cycles. But what if you are not on an agile team? Can you still take these practices and add more quality to your testing. Absolutely! These six testing practices are just good food. They will provide great value for your team as well as the project or product you are working on. This presentation will define what the practices are and what their benefits are to the team. 2 January 30, 2007

3 Jean McAuliffe Responsibilities Trainer: Agile Testing, Implementing Scrum, Agile Life-Cycle Management with VersionOne Lean-Agile coach Background Certified Scrum Master - Practitioner Senior QA Manager, Rational RequisitePro Product Manager Rally Software, Walking Orbit Agility years since 2003 Contact Jean.McAuliffe@netobjectives.com 3 January 30, 2007

4 Lean Agile Testing Practices 1. TDD & Unit Testing (Developer Testing) 2. Continuous Integration/Build Process/Version Control 3. Worry-Based Testing 4. Test-Driven not Defect-Driven 5. Exploratory Testing 6. Acceptance Testing 4 January 30, 2007

5 TDD and Unit Testing Developer Testing, Technology Facing Tests 5 January 30, 2007

6 Unit Testing Goal is easy, fast testing that provides value Tests the individual modules or units of the source code Want to test at the smallest testable unit in OOD this is the Class object Should be independent Typically uses Mock Objects to assist testing of the unit in isolation Validates each individual part is correct Doesn t validate any path or flow 6 January 30, 2007

7 So What Exactly is TDD? Test-Driven Development (Design) Uses unit testing as the test Grew out of Extreme Programming in early 2000 s Practice write a test that fails first, then write code to make it pass Test Infected - Programmers learning to love writing tests because of the paradigm shift about design, not just testing. Recognition of the value it adds to development and quality of the software. 7 January 30, 2007

8 Specific TDD Steps 1. Write a test that expresses an intent of a class in the system 2. Stub out the class (enough to allow the test to compile 3. Fail the test (don't skip this) 4. Change the class just enough to pass the test 5. Pass the test 6. Examine the class for coupling, cohesion, redundancy, and clarity problems. Refactor. 7. Pass the test 8. Return to 1. until all intentions are expressed 8 January 30, 2007

9 Continuous Integration The Engine that Drives Agility 9 January 30, 2007

10 Practices of Continuous Integration Maintain a Single Source Repository Automate the Build Make Your Build Self-Testing Everyone Commits at least Every Day Every Commit Should Build the Mainline on an Integration Machine Keep the Build Fast Test in a Clone of the Production Environment Make it Easy for Anyone to Get the Latest Executable Everyone can see what's happening Automate Deployment 10 January 30, 2007

11 Make the Build Self-Testing How many times as a tester have you gotten a new build and it fails on the first thing you try? Goal here is to have the build check itself come up with a suite of automated tests to verify For a build to be self-testing the failure of a test should cause the build to fail. Unit tests Acceptance Tests (Fit/FitNesse, Selenium, Watir) Imperfect tests, run frequently, are much better than perfect tests that are never written at all (Fowler) Adopt a culture of Don t break the build 11 January 30, 2007

12 Frequent Commits At least every day Developers find conflict quickly narrows the search for problems Find and fix in near-real time, not weeks later Developers commit by stories or smaller chunks of work 12 January 30, 2007

13 Everyone Can See What's Happening All about visibility information radiators Lava Lamps * CruiseControl * website status notification So what happens when the failed build notification gets sent to everyone? * See appendix for location information 13 January 30, 2007

14 Cruise Control Result 14 January 30, 2007

15 Worry-Based Testing How much testing do we really need? Typical worries Are we testing the right thing? Do we have over-coverage in some areas, undercoverage in others? Are we spending our time effectively? Is the overall quality going up? Is the customer(s) satisfied with our software? Do we never have enough time to do it right, but then have to find a time to do it over? Where are our biggest risks? 15 January 30, 2007

16 Crystal Project Considerations From Alistair Cockburn System Criticality Comfort Discretionary Money Essential Money Life What is the damage effect on the system if something fails? Is it just annoyed customers, losing some customers and money, or maybe it will cause you to go bankrupt, or possibly the worst scenario that somebody could die? 16 January 30, 2007

17 Worry Tasks XP and Mike Clark Let the customer decide on the quality level want more exhaustive testing, or deliver sooner? Brian Marick Assign Worry Tasks focus on the area that is causing the biggest worry. Ensure the quality meets these goals 17 January 30, 2007

18 How Do We Apply This? What is the simplest (easiest) testing that could possibly work? What is guaranteed never to have defects? Code that is never needed and never written How does knowing our criticality score change our testing approach? What is good enough testing? J.B Rainsberger: Keep testing until fear turns to boredom 18 January 30, 2007

19 Tests, not Defects? How to be truly Test-Driven and avoid Defect-Driven Nightmares 19 January 30, 2007

20 How Did We Get Defect-Driven? Easy to log a defect Easy to track status Easy to track metrics create pretty charts/graphs But be Careful what you Measure! Dilbert Cartoon I m going to build me a Winnebago! It is what we have always done Developers respond to them 20 January 30, 2007

21 Test-Driven, Not Defect-Driven Stop-the-line mentality Figure out what is wrong before proceeding Change the process to avoid defects in the first place There is waste in creating yet another artifact to track Delays introduced? Is there anything defects provide that failing tests can not? Would there be a right time for tracking defects? 21 January 30, 2007

22 Exploratory Testing Testing in a Different State of Mind 22 January 30, 2007

23 What is Exploratory Testing? Test the total product Assume a role (user + persona) to test and view the product from this perspective Have fun should be lively Test what scares you risky business Time boxed of course! 23 January 30, 2007

24 Why Do It? Learn today enough of what users would tell you in two months End of release ritual get whole company involved interested stakeholders have the opportunity to add real business value Discover new information look at the software in a new light You will find very interesting (maybe strange?) things 24 January 30, 2007

25 Taking Notes Used Skype in the past works well to capture notes, especially if you are not all in the same room Capture Issues, Questions & Anomalies It would be easier to test if you changed/added How does work? Is this important to test? How should I test it? I saw something strange Record-Playback tools could be useful 25 January 30, 2007

26 Acceptance Testing aka Story Testing, Customer Facing, Business- Facing Testing, Iteration Testing 26 January 30, 2007

27 Acceptance Testing in Agile Goal is to accept the User Story in the Iteration passing acceptance tests Different focus from unit tests Tests at a higher level than object level typically just below the GUI or at the GUI Purpose is to reflect doneness at the customer level accepted 27 January 30, 2007

28 Use FitNesse for Your Acceptance Tests Testers write acceptance tests in tables on the FitNesse wiki Developers are needed to write the fixtures The framework knows how to parse the tables 28 January 30, 2007

29 Example of FitNesse 29 January 30, 2007

30 Summary of Benefits TDD and Unit testing Find problems earlier and easier Continuous Integration Never far from good Don t Break the Build mentality Test-Driven over Defect Driven Reduces delays Track the right thing get right thing (passing tests) Worry-Based Testing Test what is important Exploratory Testing Get everyone involved and learning Find unexpected things Acceptance Testing Need for automation, makes you think about where you are testing Test early and often 30 January 30, 2007

31 Thank You! Questions? 31 January 30, 2007

32 Bibliography Full bibliography at 32 January 30, 2007

33 Bibliography Agile Testing Developer Testing tml Test-Driven Development By Example Kent Beck Scripting for Testers New book by Brian Merick coming soon! Acceptance Testing Testing Extreme Programming, Crispin, House Lessons Learned in Software Testing A context- Driven Approach. Cem Kaner, James Back, Bret Pettichord.- Not really specific to agile, but a great reference 33 January 30, 2007

34 Fit/FitNesse Introduction to Fit and FitNesse - Kris Johnson ntroduction-to-fit-and-fitnesse.html Fit for Developing Software: Framework for Integrated Tests, Mugridge, Cunningham. The book on Fit. 34 January 30, 2007

35 FitNesse Cont Fitnesse tutorials ( Getting Fit with.net - Quick Introduction to Testing.Net Applications with FitNesse Gojko Adzic FitNesse User Guide: 35 January 30, 2007

36 Bibliography CI Pragmatic Project Automation How to Build, Deploy, and Monitor Java Applications. Mike Clark Pragmatic Version Control Using CVS. David Thomas, Andrew Hunt ation.html 36 January 30, 2007

37 Bibliography Other Collaboration Explained. Jean Tabaka Agile Retrospectives Making Good Teams Great. Esther Derby, Diana Larsen Fearless Change Patterns for Introducing New Ideas. Mary Lynn Manns, Linda Rising Managing Transitions Making the Most of Change. William Bridges The Art of Possibility Transforming Professional and Personal Life. Rosamund Stone Zander, Benjamin Zander 37 January 30, 2007

38 Source Code Management Open Source Subversion ( (built on CVS) CVS still popular ( Hosted: Commercial Perforce ( 38 January 30, 2007

39 Testing Tools Fit Framework for Integrated Tests Fitnesse Team Use of Fit Fitnesse.org GUI Tools Canoo Web Test - Watir - Selenium - Abbot - Systir - Software Testing Tool Finder: 39 January 30, 2007

40 More Tools Unit Testing JUnit - NUnit - Agile Project Management Version One - Rally - Target Process January 30, 2007

a brief introduction to creating quality software continuously Copyright 2011 Davisbase, LLC

a brief introduction to creating quality software continuously Andy Painter Agile Coach/Trainer/Consultant CSM, CSP, CSD Instructor andy@davisbase.org (704) 835-0194 Interests: Cloud Computing, Agile Development