The Good Testing, The Bad Testing and The Ugly Testing
summary
Describes why central regression teams fail: a 200–250 person org with 15 dev teams throws three weeks of work over a wall, then removes the regression team and redistributed testers who mostly leave. Demonstrates exploratory techniques (mind maps, user heuristics), warns against brittle automation and counters with a pragmatic tea rule for fast suites, and cites a simple data-tool called equal test helper that speeds exploratory work and reduces risk.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:56Let's Talk About The Bad...
- 8:39"The misguided belief that testers test and programmers code, and the separation of the two disciplines is important" Elisabeth Hendrickson
- 17:12Testing is just following scripts?
- 25:20So What Is Good Testing?
- 26:07Risk Reduction for Appropriate Quality
- 32:00Automate (a lot)
- 33:37Tea Exploits Present Bias
- 37:36Teams value quality A testers job is to help their team understand what quality means
related talks
43mRegression Obsession
45mImproved Regression Testing in Agile
34mesting in modern times: A story about quality and value
16mChallenges of Testing at Scale | Experiments and Experiences
57mOptimizing Your Testing Team
58mTesting Strategy - New Model, Better Outcomes
37mThe Lazy Tester
45mSerendipity and Perseverance — Injecting Testing in a Test-Resistant Team