A Game of Testing
summary
Shows a concrete process: builds gamified ticket/achievement system to reward fixes, rolls releases to a small percent of users, and adds lightweight automation (unit tests and Selenium) plus Kanban with WIP limits and cycle‑time metrics. The team measures effects: cycle time drops ~40% and production incidents fall ~50%. Explains which scripts and dashboards are used, how badges map to bonuses, and which changes fail so the delivery loop actually tightens.
AI-written summary · about
chapters (9)
- 0:00Introduction to testing game
- 3:03Starting a project from scratch
- 7:18Gamification of testing
- 13:07Task prioritization and time management
- 18:24Product owner's role in testing
- 24:57Improving software delivery
- 30:07Automated testing and unit tests
- 33:47Release preparation and launch
- 37:29Conclusion and testing tips
related talks
37mTesting Games
53mTransforming testing methodologies: From manual to robust strategies
40mScaling testing & test automation without losing control
56mThe End Game
26mThe Impact of Testing on a DevOps Pipeline
32mClimbing the Mountain of CI/CD: A Tester’s Tale
33mTESTING IN PRODUCTION
31m#testedAF: Test All the Things (Not Just Your Units)