Serendipity and Perseverance — Injecting Testing in a Test-Resistant Team
summary
One tester joins a team with 1 tester to 10 developers, finds logging shows 10% of logged-in customers see program errors (reduced to ~1%), throws away bloated specs (39 pages → two-line checklist), rewrites four of twelve processes, adds a remote exploratory tester from Romania, runs monthly Selenium UI tests and integrates them into check-ins, creates a recurring test/fix/finalize week, and uncovers 150 issues in a single feature while nudging developers toward unit testing and incremental automation.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:14An Experience Report
- 10:54How We See Development and Testing
- 21:28Approaches to Change Unit First Tester
- 34:58The Current Challenges
- 36:08Serendipity and Perseverance
- 42:04Learning About My Team
related talks
55mTest Management Revisited
59mBabble & Dabble: Creating Bonds Across Disciplines
37mThe Lazy Tester
36mWhole team quality: In the same boat or up the creek?
08m“Testers! Aim to Enable”
39mThe Good Testing, The Bad Testing and The Ugly Testing
45mBuilding Tools to Free up Exploratory Testers
36mContext-driven Agile Tester