Testing in a DevOps team
Download as PPTX, PDF1 like1,226 views
The document discusses the evolution of testing practices from a traditional waterfall model to a more agile DevOps approach with cloud-based behavior-driven development (BDD). It emphasizes the importance of speed in feedback loops, the necessity of aligning testing with business value, and the use of a testing matrix for decision-making on new features. Key considerations include automation reliability, CI process integration, and maintaining documentation and shared understanding.
Testing in a DevOps team
- 1. Shift left and shift right - the testing swing - Laurent Py [email protected] @py_laurent blog.hiptest.net
- 2. From waterfall (2003)… Product: Test Designer, eclipse plug-in in JAVA • Waterfall process • 1 release every 6 months • Few tests and no TDD • 1 month (x5 people) to do release testing before deployment
- 3. …to DevOps Product: Hiptest, BDD in the cloud • Mix of Scrum&Kanban process • We do BDD • Multiple deployments a day • Acceptance tests are part of the CI process
- 4. Break silos
- 5. It’s all about speed of feedback loop
- 6. It’s about speed of feedback loop “I like what I've seen so far and I've been very impressed with the live support. Your team managed to identify and fix a bug I'd found within about 12 hours.” Tom Graham Product Innovation Software Manager
- 7. How to ensure quality of deliverables?
- 9. Why? Is it worth doing it?
- 10. Put value before correctness 1. Why? Is it worth doing it? 2. How to ensure quality of deliverables?
- 11. The testing matrix we use today Build Production New Feature/ experiment What should we build and why? Is it really worth it? Validated feature How to automate? Is it really reliable and does it scale?
- 12. The testing matrix we use today Build Production New Feature/ experiment What should we build and why? Is it really worth it? Validated feature How to automate? Is it really reliable and does it scale?
- 13. Behavior driven development: • Create shared understanding based on examples • Using a common business terminology • Define the stop • Live specification & documentation when automated What should we build?1
- 14. What should we build?1
- 15. What should we build?1
- 16. Challenge business assumptions Why should we build it?1
- 17. As a Product Owner I want to link a Hiptest scenario with a Jira issue So that I can get traceability between tests, user stories and issues Why should we build it?1 +
- 18. The testing matrix we use today Build Production New Feature/ experiment What should we build and why? Is it really worth it? Validated feature How to automate? Is it really reliable and does it scale?
- 19. / Is it really worth it?2
- 20. Is it really worth it?2
- 21. Is it really worth it?2
- 22. The testing matrix we use today Build Production New Feature/ experiment What should we build and why? Is it really worth it? Validated feature How to automate? Is it really reliable and does it scale?
- 27. Key success factors3 Refactoring CI+
- 28. The testing matrix we use today Build Production New Feature/ experiment What should we build and why? Is it really worth it? Validated feature How to automate? Is it really reliable and does it scale?
- 29. Is it reliable and does it scale?4
- 30. The testing matrix we use today Build Production New Feature/ experiment What should we build and why? Is it really worth it? Validated feature How to automate? Is it really reliable and does it scale?
- 31. The tools we use today
- 32. To the test managers