Continuous Testing

Transcript

1. CONTINUOUS TESTING ♾ @garyfleming
2. A(GILE) DISSERVICE
5. THROWING IT OVER THE FENCE ☹
6. TOO LATE ⏰
7. CONTINUOUS INTEGRATION AND DELIVERY
8. CONTINUOUS INTEGRATION All developers/testers merge their code to a shared mainline at least once a day.
9. CONTINUOUS INTEGRATION ➤ Branching disappears (move to Trunk-Based Development) ➤ Code sees each other much sooner (less isolation) ➤ Quality/tests need a massive boost, if lacking
10. CONTINUOUS DELIVERY All changes go to production; safely, quickly, and sustainably.
11. WE HAVE A PROBLEM (SUMMARY SO FAR) ➤ Lots of places use Test Columns ➤ Getting perspectives too late ➤ CI/CD are only going to make this a less viable strategy
12. STRATEGIES FOR SUCCESS Three Things
13. A LITTLE MORE CONVERSATION (A little less action, please)
14. THREE AMIGOS ➤ Who: Business, Build, Quality ➤ What: Discussion about shape, size, oddities of a story ➤ Why: Alignment, wider perspective, catch issues earlier
15. YET ANOTHER MEETING? :(
17. ➤ Too many Questions? ➤ Too many Rules? ➤ Too many Examples? ➤ Too few Examples? ➤ Taking too long?
18. CONTROL AND COMMAND Strategy 2
19. FEATURE TOGGLES Deployment is not Release
20. TOGGLES
21. TOGGLES
22. MAKE TOGGLES PART OF YOUR CONVERSATIONS!
23. FIXING TOGGLE ISSUES ➤ Lots of tangled toggles? Stop. Redesign. Refactor ➤ Too many toggles? Consider if you really need them all. ➤ Unsafe features going to production? Ask for toggles
24. A COACHING MINDSET Strategy 3
25. QUALITY RESPONSIBILITY
26. HOW? WHAT? IT DEPENDS!
28. NOT ONLY SHIFT LEFT ⬅➡↗↘⬇⬆↙↖↕↔↪⤵⤴↩
29. NOT FOR YOU? (That’s okay )
30. SUMMARY ➤ Process: Example Mapping ➤ Technical: Feature Toggles ➤ Mindset: Coaching ➤ ... and beyond.
31. THANK YOU @garyfleming