Everything the Tester in your life wants you to know but is too afraid to tell you
summary
Claims that matter: a Formula 1 simulation shows 20–30s on racekit but 3s in air‑conditioned lab because of a toy laptop overheating at the track, and a shipped title, Bad Boys 2: Miami Takedown, proves decisions about control mapping break usability. Testers report moving from bug hunting to prevention, build small tools, and do glue work to fix the organization; automation is a tactic not a panacea, risk‑focused choices and early inclusion change outcomes.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:12Devs versus testers
- 6:31Tester career arc
- 12:27Glue work in testing
- 13:09Why testing is a detective’s dream job
- 15:16What devs love about coding
- 18:24Testers as delivery heroes
- 22:56Unpopular tester truths
- 24:02Bugs beyond 'my machine'
- 25:11Testing timelines
- 27:21Production bugs
- 29:50Early tester inclusion
- 32:59Automation isn’t always the answer
- 35:30Curiosity over blame
- 36:16Helping testers benefits devs
- 37:26Q&A
related talks
53mLife of a Tester: From Once Upon
15mThe Tester I Was and the Tester I Could Be
23mA TESTER’S LIFE IN THE AUTOMOTIVE INDUSTRY
44mTest First Saves the World
44mTest Intelligence: Finding More Bugs in Less Time with AI
32mWhy testing is a developer's problem
24mThe more we test, the worse?
41mExits on the (QA) Highway to Hell
