Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Testing FAQs and Mythbuster - Software Testing Atlanta Conference 2015

2,464 views

Published on

Agile brings us many challenges (and opportunities!) to the world of testing. Through his work in the trenches, Uval has encountered many testing professionals who struggle with agile. Some of these struggles are due to following "by the book" practices without understanding the underlying principles. Others are due to myths being spread. In this presentation, Uval will share these struggles and questions that testers and their managers often face, and recommend answers. Participants will leave with a better understanding of what agile really means for a testing organization, processes, and the profession, and will be better positioned to support and champion a change towards real agility in their organization.

Published in: Software

Agile Testing FAQs and Mythbuster - Software Testing Atlanta Conference 2015

  1. 1. @yuvalyeret #STAC15 Agile Tes5ng FAQs and Mythbuster Yuval Yeret - AgileSparks #STAC15 1
  2. 2. @yuvalyeret #STAC15 Agile Team2 Agile Team1 Ongoing Done Features Backlog Develop Feature/ Sprint in Progress Story-level Test & Fix Deploy ment Done Ongoing Done Stories Backlog Ongoing Specify Done A B C G H J K L M H.6 H.0 H.1H.2 H.3 H.4H.5 D2 D3 T2 T1 D1 P 1 H.7 T2 Implement Feature by Stories How does an agile project/program looks like? (by the book…)
  3. 3. @yuvalyeret #STAC15 But when the typical dev/test group meets Agile… See Kent Beck’s idea as described by Markus Gartner at hKp://www.shino.de/2010/11/04/soQware-g-forces-the-effects-of-accelera5on/
  4. 4. Agile Team2 Agile Team1 Ongoing Done Features Backlog Develop Feature/ Sprint in Progress Story-level Test & Fix Deploym ent Done Ongoing Done Stories Backlog End of Release Testing Ongoing DoneOngoing Specify Done D E F A B C G H J K L M H.6 H.0 H.1H.2 H.3 H.4H.5 D2 D3 T2 T1 D1 P1 H.7 T2 Implement Feature by Stories UAT Regression Performance Security Functional Progression Exploratory ATDD Auto Long wait for the endgame Real Life… Not so agile testing... “Sprint is too short for everything we need to achieve DONE” “Let’s leave the serious testing for the release testing phase” The 2-level Test Strategy Pyramid – Story + Release-level Platform Matrix Real Network
  5. 5. @yuvalyeret #STAC15 The result - only a limited amount of feedback is early and effective 0 20 40 60 80 100 120 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 done done done 40% 60% Iden5fy coverage that happens outside the sprint. Which is the biggest quality risk if found late?
  6. 6. Agile Team2 Agile Team1 Ongoing Done Features
 Backlog Develop Feature/
 Sprint
 in 
 Progress Story-level 
 Test & Fix Deploym ent Done Ongoing Done Stories Backlog Ready For
 Feature Test Test Feature- level Ongoing Done End of Release Testing Ongoing Done Ongoing Specify Done D E T F T T A B C G H J K L M H.6 H.0 H.1 H.2 H.3 H.4 H.5 D2 D3 T2 T1 D1 P1 H.7 T2 Implement Feature by Stories UAT Regression Performance Security Functional Progression Exploratory Try - Slowly shifting left towards Continuous Quality and adding the Feature-level testing stage in the pipeline Add Feature/Epic level testing 1.  Add Feature/Epic/ Iteration level testing. 2. left-shift more and more testing through automation, enabling teams using environments/tools/knowhow and more.
  7. 7. @yuvalyeret #STAC15 Role of tes5ng is to find defects to assure quality Elaborate Requirements Technical Design Coding / Unit Tes5ng Test Execu5on + Fixing Done Test Design Test Automa5on Myth or Best Prac5ce?
  8. 8. @yuvalyeret #STAC15 8
  9. 9. @yuvalyeret #STAC15 • Most expensive automa5on to develop, run & maintain, so minimize!!! • Move majority of E2E tes5ng coverage to Service/API layer • QTP/UFT/Selenium/PerfectoMobile/etc. UI • “The Workhorse” of enterprise agile tes5ng • Created by testers & developers on agile teams supported by frameworks/guidance by Automa5on CoE • soapUI, etc. Acceptance (Service/API) • Leverage Agile Teams developer tes5ng to reduce coverage needs • Ability to automa5cally detect (through coverage tools etc.) what is covered Unit Tes5ng Manual hKp://www.mountaingoatsoQware.com/blog/ the-forgoKen-layer-of-the-test-automa5on- pyramid If we accept the test automa5on pyramid what does it mean for Tester Skills? Myth or Best Prac5ce?
  10. 10. 10 Credit - Udi Weinberg – HP SoQware
  11. 11. @yuvalyeret #STAC15 Best Prac5ce – Agile Testers DRIVE quality
  12. 12. @yuvalyeret #STAC15 ATDD = Acceptance Test Driven Development - Build Quality Into Design – preven5ng defects rather than just finding them Elaborate Requirements Test Design Technical Design Coding / Unit Tes5ng Test Execu5on + Fixing Done 1.  ATDD Thinking Use test scenarios to guide design (which can then happen using TDD, or not…) hKp://www.agilesparks.com/test-first-reading-list Test Automa5on ATDD/BDD - The Enterprise/ Real-world wrapper for TDD…
  13. 13. @yuvalyeret #STAC15 Automation is a USEFUL skill for Testers/ Quality Engineers. NOT their core skill! It IS a core team capability for enabling Continuous Quality
  14. 14. @yuvalyeret #STAC15 The Future?* *AgileSparks predic5on 2005 2010 2015 2020 SW Developers Testers SW Engineers Automa5on Experts Test Engineers/ Experts
  15. 15. @yuvalyeret #STAC15 User Story 1578 •  Acceptance Criteria: –  Scenario 1 –  Scenario 2 –  Scenario 3 –  Scenario 4 –  Scenario 5 –  Scenario 6 –  Scenario 7 –  Scenario 8 –  Scenario 9 –  Scenario 10 –  Scenario 11 15 What do you think? Is this a good story? What do you like about it? How would you improve?
  16. 16. Agile Team2 Agile Team1 Ongoing Done Features
 Backlog Develop Feature/
 Sprint
 in 
 Progress Story-level 
 Test & Fix Deploym ent Done Ongoing Done Stories Backlog Ready For
 Feature Test Test Feature- level Ongoing Done End of Release Testing Ongoing Done Ongoing Specify Done D E T F T T A B C G H J K L M H.6 H.0 H.1 H.2 H.3 H.4 H.5 D2 D3 T2 T1 H.7 T2 Implement Feature by Stories Specify/Groom using Acceptance Tests Backlog Grooming / Acceptance-Tests Specification Workshop •  Identify acceptance criteria/tests for the next stories in the backlog. •  Use acceptance tests as guidance for slicing stories smaller to enable more effective agile collaboration
  17. 17. @yuvalyeret #STAC15 Acceptance Tests/Mini- Stories Stories MMFs Features Feature MMF H Story H1 Test for H1 Mini-story H4 Mini-story H5 Story H2 Story H3 MMF I MMF J MMF K Testers are key to effective grooming together with the PO and the Devs!!!
  18. 18. @yuvalyeret #STAC15 Ques5ons? •  hKp://www.agilesparks.com/agile-tes5ng-reading-list •  hKp://www.agilesparks.com/Services/AgileTes5ng •  Blogging at yuvalyeret.com •  Email me ques5ons/feedback/sugges5ons at yuval@agilesparks.com or 857-218-9585 •  Unlock my Agile Tes5ng Workshop in your city! •  These slides will be up at hKp://www.slideshare.net/yyeret soon. My other talks are already there… 18
  19. 19. @yuvalyeret #STAC15 Devops Tools Tradi5onal Processes Ideal Batch w/o Con5nuous Quality Investment Reduce Batch Size Further WITH Great automa5on and leaner processes Con5nuous Quality is a journey with lots of value at each step

×