Exits on the (QA) Highway to Hell
summary
Lists 10 concrete bad practices and gives remedies: use product risk assessment / customer value poker to prioritize; don’t replace testers with devs or blind automation — automate only after manual verification and use test design techniques to measure coverage; testing levels described (unit, integration, system, nonfunctional, end‑to‑end); example: a 1,400 ft glass bridge passes component tests but needs production fixes for wind; example: TaskCoach shows 16 defects yet 95% user approval, so bugs don’t always mean no value.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:56Success stories aren't enough
- 4:44Micromanaging managers
- 8:43Ignoring testers
- 11:17Chang Chai Chi Bridge analogy
- 17:45Testing in production
- 20:41Speeding up testing fails
- 25:50Relying on standard components
- 28:02Not everything automated
- 31:13Testing is more than bug hunting
- 35:46Supplier testing promises
- 37:11Test design essential
- 38:37Ten bad practices
- 40:24Communication is key
related talks
15mHow to NOT waste time
01h 04mBuilding on Success, Beyond the Obvious
50mThe End of Testing as We Know It
54mTest Automation Transformation Avoiding the 7 Common Pitfalls
41mThe Tester’s Guide to Quality
56mNo QA resources? You can still deliver a quality website
57mAdvanced Testing Techniques: Tips from the trenches
31mZen of Testing