Overcoming the obstacles of Exploratory Testing at scale
summary
Claims a measurable framework: session based testing with two‑hour slots (briefing, 1h testing, 30m doc/debrief), use of tour based testing and thinking‑hats, and a requirement‑linked scope. Scaled work across 5→30 agile teams, weekly sessions cut mean time to feedback and show that 88% of bugs found wouldn’t have appeared in regression suites; tracked metrics include production defects, severity, defect variety, mean time to feedback and regression leak, and the process yields reproducible, aggregateable results.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:40Problem of Scaling
- 2:19Three Major Problems with Scaling
- 3:21Why Is It So Hard To Scale Exploratory Testing
- 6:07Session Based Testing
- 6:57Tor Based Testing
- 8:08The Six Thinking Hats
- 8:45Scenario Based Testing
- 10:52Consistency
- 11:25Trust
- 11:44Intensity
- 13:17The Mean Time to Feedback
- 14:11Formal Testing as a Change Detector
- 19:27What Is the Source for Your Presented Numbers and Graph
related talks
42mExploratory Testing Basics, Experiences and Future
36mContext-driven Agile Tester
31m#testedAF: Test All the Things (Not Just Your Units)
59mBabble & Dabble: Creating Bonds Across Disciplines
49mTest Strategy in a SCRUM Environment
16mChallenges of Testing at Scale | Experiments and Experiences
37mTesting: The compass for creative exploration
24mImproving Development Quality and Speed with Agile Testing