What is agile_testing

444 views
406 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
444
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

What is agile_testing

  1. 1. What is AgileTesting? key success factors & practices presented by: in partnership with:
  2. 2. IntroductionAndy Painter • Agile Coach/Trainer/Practitioner • CSM, CSP, CSD Instructor • andy@davisbase.org • (704) 835-0194 http://www.linkedin.com/in/andypainter @_andy_painter Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  3. 3. Testing in Your WorldNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead ofjust documenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  4. 4. What is our Desired State? Let’s ask the practitioners that are ALREADY where you want to BE a simple question:“Why do you loveAgile Testing?” Source: http://www.infoq.com/news/2009/06/love_agile_testing Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  5. 5. AutomationNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  6. 6. CollaborationNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  7. 7. Test Driven DevelopmentNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  8. 8. Continuous ProcessNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  9. 9. One TeamNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  10. 10. Collective OwnershipNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  11. 11. FeedbackNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  12. 12. SupportiveNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  13. 13. Focus on QualityNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team oriented QUALITYTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  14. 14. Test FirstNo more manual test scripts!Developers actually like me!Now I can break features before theyre written!Automated test results appear many times a dayThe atmosphere is very team orientedTester can fix the occasionally bugProvides the opportunity to constantly review TestPracticesI spend much, much less time debuggingThe chance to actually impact quality instead of justdocumenting it!Theres always time for testing, because testinghappens first Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  15. 15. Top 10 Reasons to Love Agile Testing1. No more manual test scripts!2. Developers actually like me!3. Now I can break features before theyre written!4. Automated test results appear many times a day5. The atmosphere is very team oriented6. Tester can fix the occasionally bug7. Provides the opportunity to constantly review Test Practices8. I spend much, much less time debugging9. The chance to actually impact quality instead of just documenting it!10. Theres always time for testing, because testing happens first Source: http://www.infoq.com/news/2009/06/love_agile_testing Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  16. 16. 10 Principles for the Agile TesterProvide Continuous FeedbackDeliver Value to the customerEnable face-to-face communicationHave courageKeep it SimplePractice continuous improvementRespond to changeSelf-organizeFocus on PeopleEnjoy Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  17. 17. Agile Tester QualitiesEnjoy learning & challengesCreativeCollaborativeOpen-mindedResults-orientedWillingness to take on any taskor roleView of the big pictureFocus on the customerPassionate Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  18. 18. Traditional vs. Agile Testing TraditionalRequirements Specification Code Test Deploy Phased Gated Time E F Iterative D D Incremental Integrated: C C C Elaborate • • Develop • Test A B A B A B A B Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  19. 19. Agile Testing Quadrants Q2 Q3 Q1 Q4 Source: Agile Testing by Lisa Crispin & Janet Gregory Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  20. 20. Mike Cohn’s Testing Pyramid Small in number Tools: Selenium, Watir, QTP At least one per Story Tools: FIT/Fitnesse, BDD At least one per class or module Tools: JUnit, xUnit Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  21. 21. Cost of Defects 20000 Catch Defects Early in the 15000 Lifecycle during design 10000 & development phases 5000 to lower TCO in short 0 term (current release) Requirements Development Maintenance and long term (future releases) Copyright 2010 Davisbase LLC. Distribution without express permission is forbiddenBased  on  a  2003  Capers  Jones  Study  of  over  4000  so7ware  projects
  22. 22. TDD Red, Green, Refactor Test Driven Development (TDD) Create a Test • Test cases, testing harnesses, testing Pass scripts are written before any coding begins. Run a Test Fail • Refactoring and development of code until testing scripts run “all green.”Make a Change • Requires developers to think of the larger solution and approach to be developed Run the Test before coding begins. Pass • Benefits include more testing integrated Refactor into development efforts, higher quality code delivered, decrease amounts of code rework later in project cycle. Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  23. 23. Acceptance Test Driven Development (ATDD) Discuss Distill Demo Develop Test Refactor Code ATDD Cycle model by Jim Shore with changes suggested by Grigori Melnick, Brian Marick, and Elizabeth Hendrickson Copyright 2010 Davisbase LLC. Distribution without express permission is forbiddenThe ATDD CycleDiscuss: work with the business stakeholders to understand their real needs and concerns. In traditional environments, this is usually called“requirements elicitation.” In the context of Agile development, the purpose of this discussion is not to gather a huge list of requirements butrather to understand what the business stakeholder needs from one particular feature. During these discussions, ask questions designed touncover assumptions, understand expectations around non-functional needs such as stability, reliability, security, etc., and explore the full scopeof work the business stakeholder is requesting.Distill: collaborate with the business stakeholders to distill their stated needs into a set of acceptance tests, or examples, that define “done.”These tests should focus on externally detectable behavior and will be expressed in tables or keywords.Develop: write the code to implement the requested feature using test- driven development (TDD).Demonstrate: show the business stakeholder the new feature in the emerging system and request feedback.
  24. 24. Automate, Automate, Automate‣ Understand how you work individually and collectively‣ Automate anything you do more than once within a task, test, story, process‣ Automation is essential to shorten feedback loops and maintain flow state Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  25. 25. Automate Early & Often‣ Steep drop off in benefits of Automation‣ Get the benefits when you need it most‣ Cost will prohibit adoption later as benefits are not easy Source: Succeeding with Agile: Software Development using Scrum, Mike Cohn seen Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  26. 26. Continuous Integration DefinedA process that supports teams in making small, working incremental changes to software. Continuous Integration is an automated process that provides feedback and supports: • Transparency • Consistency • Continuous Builds • Continuous Inspections • Continuous Testing Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  27. 27. Challenges & Constraints‣ Organizational Culture‣ Existing Processes & Models‣ Knowledge, Training, Understanding‣ Organization Size‣ Roles & Identities‣ Past Experiences & Attitudes Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  28. 28. Iterating to Testing Agility‣ Keep a Backlog & Prioritize Regularly‣ Realize Constraints‣ Keep Moving Forward‣ Automate ‣ Automate ‣ Automate Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  29. 29. Improvement BacklogStart! Example: • Increase Test AutomationKeep a Improvement • Enable teams to use ContinuousBacklog Integration • Adopt TDDTrack Progress • Increase Code Coveragetoward Goals • Continuous Deployment Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  30. 30. Top 5 Key Contributors to Success‣ People ‣ Test Continuously‣ Test First ‣ Collaborate in response to Feedback‣ Automate Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  31. 31. Suggested ReadingCopyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  32. 32. Your Questions, My AnswersNote: For those questions we do not have time to answer during thewebinar, I will be providing a written response. Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  33. 33. How to Claim Your PDU‣ Go to ccrs.pmi.org‣ Search for ASPE as a Registered Education Provider. Our number is 2161.‣ At the bottom of our details page, select “See Provider’s Activities”‣ Find the activity and code stated by the ASPE moderator during the seminar‣ The seminars are typically a Category 3 for one PDU Webinar Code: Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  34. 34. Meeting Close‣ Thank you.‣ Andy Painter, Davisbase Consulting‣ andy@davisbase.org‣ http://www.davisbase.org‣ (704) 835-0194 Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden
  35. 35. About Davisbase Consulting‣ A leading, national provider of Agile training and coaching services. ‣ Since 2007, over 300 classes taught to over 5000 people nationwide. ‣ Training, coaching, and consulting work for over 50 Fortune 500 Clients.‣ Experienced. “In the trenches” doing what we teach ‣ Extensive experience with all aspects of software development and project lifecycle across multiple industries and verticals. ‣ Every title and role from Developer, QA, Project Manager through Sr. Leadership. ‣ Average of 15+ years of applied IT Leadership experience. Copyright 2010 Davisbase LLC. Distribution without express permission is forbidden

×