Testing Games
summary
Describes a game-development testing and delivery setup that uses unit, API and UI tests plus mobile automation to enable continuous delivery with deploys reduced to hours. Uses a canary release flow, two production-like environments, Kanban with strict WIP limits and short tasks, measures lead time and per-team cycle time, runs rapid incident committees and SMART root-cause reviews, and adds a points-based gamification wallet redeemable for real rewards; most changes reportedly reduced cycle time.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:08Project conditions
- 6:20Project terminology
- 8:29Team communication
- 10:38Priority fixes
- 12:23Defect analysis
- 13:05Attribute matrix
- 15:32User needs
- 16:12Task definitions
- 17:38SWOT analysis
- 19:20Process logging
- 20:03Motivation & gamification
- 23:33Kanban processes
- 29:57Continuous Delivery
- 33:51Feature flags & canary
- 34:14Project workflow
- 36:44Summary & Q&A
related talks
38mA Game of Testing
49mThe Whole Team Approach to Testing in Continuous Delivery
42mTesting in a Continuous Delivery World
41mShift Left, Shift Right and Improve the Centre
31m#testedAF: Test All the Things (Not Just Your Units)
22mTesting in Production
49mBalancing Release & Sprint Delivery Speed with Thorough Testing
33mTESTING IN PRODUCTION