How to Talk about Coverage
summary
Argues that coverage equals communicated risk and shows concrete techniques to make trade-offs instead of guessing: five trivial stories generate 4,000 scenario combinatorial explosion, use timeboxing and priority cut lines to decide what to test, build a simple heat-map dashboard or spreadsheet to visualize coverage and defects, use mind maps, decision trees, Selenium automation, Hexawise pairwise generation and a testing Kanban to manage emergent risks. Demonstrates a dashboard and process that caught executive attention and changed release decisions.
AI-written summary · about
chapters (17)
- 0:00Intro
- 5:05Value
- 5:49combinatorial explosion
- 9:38coverage of what
- 10:40testing
- 12:24regression testing
- 17:30priorities
- 19:04legacy applications
- 22:47vision maps
- 24:47decision trees
- 25:51heat map
- 27:03combinatorial explosions
- 28:07customer example
- 30:42Gmail architecture
- 32:47Testing Kanban board
- 35:23Models
- 37:52Conclusion
related talks
53mReady to Run the Risk? - Applying a Risk-Based Approach to Testing
51mDebunking Myths Around Test Coverage
01h 00mRequirement Coverage: Myth or an Ultimate Goal
01h 04mBuilding on Success, Beyond the Obvious
28mYour Testing Strategy is broken - lets fix it!
49mTest Coverage Myth Busted: Test-to-Code Map and Test Impact Analytics
49mTest Coverage Visualization
15mHow to NOT waste time