Mike Talks (Datacom)
1 like1,000 views
The document discusses transitioning from a traditional waterfall testing model to an agile testing model. It advocates focusing on the needs of the customer rather than rigid processes and deliverables. An effective agile testing approach focuses on relationships, lightweight processes, transparency, and making testing work visible. Testers should avoid the "cargo cult" trap of using old procedures just because and should continuously review and improve testing practices.
![Test Reporting
What testing is
complete?
What problems have
there been?
[Defects]
What testing have
we done?](https://image.slidesharecdn.com/miketalksagilenz-deprogrammingthecargocultagilenzconferencesconflictedcopy-150909015045-lva1-app6892/85/Mike-Talks-Datacom-24-320.jpg)
![That’s a lot of questions …
What testing is
complete?
What problems
have there
been?
[Defects]
What testing
have we done?
What testing are
we going to do?
What
requirement/
feature are we
testing?
What testing
have we done?
How do new
testers learn/ test
on the system?
What are we
going to test?
Who is going to
test?
How long is it
going to take?
How do we go
about delivering
testing?](https://image.slidesharecdn.com/miketalksagilenz-deprogrammingthecargocultagilenzconferencesconflictedcopy-150909015045-lva1-app6892/85/Mike-Talks-Datacom-25-320.jpg)
![Testing Cycle 3: Doing
The Testing (pt3) –
Problems!
What problems have
there been?
[Defects]](https://image.slidesharecdn.com/miketalksagilenz-deprogrammingthecargocultagilenzconferencesconflictedcopy-150909015045-lva1-app6892/85/Mike-Talks-Datacom-42-320.jpg)
Mike Talks (Datacom)
- 1. Deprogramming the cargo cult of testing Mike Talks Datacom
- 2. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Who are we?
- 3. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 • RealMe developed as “classic” V-model • 18 months between inception and delivery • 6 weeks of system testing alone A long time ago …
- 4. Being a “classic” V-model System Test UAT
- 5. As RealMe matured … DIA needed to respond more to their customers’ needs
- 6. Rethinking the model Going agile … Where does this leave testing?
- 7. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Take what you’ve always done … The ultimate temptation
- 8. This is the Cargo Cult trap • Project context changes • Use same procedures • Expect same result
- 9. Waterfall l Deliver EVERYthing l 12 months from inception l 6 weeks for testing l 7 testers In a nutshell Agile • Deliver SOMEthing • 2 weeks from inception • 2 weeks for testing • 2 testers
- 10. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 As a test professional … How do you begin the process of change?
- 11. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Initiate change By requiring a change in contract with your customer?
- 12. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Initiate change By manda5ng a new set of test processes?
- 13. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Initiate change Implemen5ng change secretly, hoping no-‐one no5ces …
- 14. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 How the deprogramming begins
- 15. Looking at the model we had Requirements Test Strategy Test Plan Test Scripts Test Reporting
- 16. How can this model go off the rails?
- 17. Derail #1: Lead time
- 19. Derail #3: Reviewing & Collaboration
- 21. Test Strategy How do we go about delivering testing?
- 22. Test Plan What are we going to test? Who is going to test? How long is it going to take?
- 23. Test Script What testing are we going to do? What requirement/ feature are we testing? What testing have we done? How do new testers learn/ test on the system?
- 24. Test Reporting What testing is complete? What problems have there been? [Defects] What testing have we done?
- 25. That’s a lot of questions … What testing is complete? What problems have there been? [Defects] What testing have we done? What testing are we going to do? What requirement/ feature are we testing? What testing have we done? How do new testers learn/ test on the system? What are we going to test? Who is going to test? How long is it going to take? How do we go about delivering testing?
- 26. Looking at it another way … as the questions they answer The deliverables don’t have as much value …
- 27. To Make Agile Testing Work … Four fundamental aims
- 29. Aim #2 Processes lightweight but address needs
- 32. Use Exploratory Testing? What testing are we going to do? What testing have we done? Common worries …
- 33. There’s always that one person asking … How will you know what to test without your scripts?
- 34. From Jon & James Bach … • “We wanted to be accountable for our work” • “We wanted to give status reports that reflected what we actually did” Session Based Test Management
- 35. • The heart of what we did. • But needed some customisation Session Based Test Management
- 36. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 How We Test On RealMe Warning! Tailored to fit
- 37. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Testing Cycle 1: Planning Testing Tasks What are we going to test?
- 38. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Testing Cycle 2: Expanding Testing Tasks (pt1) Boundaries? Browsers? Related areas? What testing are we going to do?
- 39. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Testing Cycle 2: Expanding Testing Tasks (pt2)
- 40. Testing Cycle 3: Doing The Testing (pt1) - Assignment What requirement/ feature are we testing?
- 41. Testing Cycle 3: Doing The Testing (pt2) - Recording What testing have we done?
- 42. Testing Cycle 3: Doing The Testing (pt3) – Problems! What problems have there been? [Defects]
- 43. Testing Cycle 3: Doing The Testing (pt4) – Peer review What testing have we done?
- 44. Testing Cycle 4: Updating the board What testing is complete? What testing have we done?
- 45. Testing Cycle 5: And right at the end …
- 46. So what’s left? Who is going to test? How long is it going to take?
- 47. But what about … How do new testers learn/ test on the system?
- 48. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Deliverables? Mind maps = Plan Recordings = Proof of testing
- 49. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 Deliverables? Sprint board = Progress Report / Defect Tracking
- 50. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 And how’s it working out? More engaged test team Happy customer Making testing visible to whole team
- 51. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 We’re replicating the success
- 52. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 The temptation is still there
- 53. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 The trap is still there …
- 54. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 We need to remember… Individuals and interactions over processes and tools
- 55. Copyright © Datacom New Zealand Limited 2013 Wednesday, 9 September 15 But we’re getting there …
- 57. Summary #2 Focus on needs, not deliverables
- 58. Summary #3 Can what you do be made more visible? Mike Lowery Agile Coach Nomad 8
- 59. Thanks for listening… Mike Talks Datacom
- 60. Question – Manual regression Use of “character cards” personas
- 61. Question – Automated checking with Selenity Datacom software • Uses Selenium drivers • Part of build checks • Delivers less buggy code to test env
- 62. Thanks for listening… Mike Talks Datacom