Ready to Run the Risk? - Applying a Risk-Based Approach to Testing
summary
Argues that a risk-adjusted test plan beats vague coverage by mapping identified risks (often 100 down to ~20 exposed) to concrete tests in a spreadsheet, scoring probability × impact (1–5 or 1–4) to compute exposure, color-coding the top 10 tests so five red tests run first. Uses a risk breakdown structure, multiplies scores for a risk matrix, ties risks to requirements, defect density, code-commit churn and Google Analytics funnels, and keeps time for exploratory testing; applied to a 20-item cyber threat list and produced useful, actionable test priorities.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:07Risk-based testing
- 3:35Risks and risk management
- 7:26Risks in software projects
- 10:55Agile practices for risk mitigation
- 13:21Risk probability and impact
- 16:32Risk exposure analysis
- 18:39Testing and technical risk
- 21:06Risks to test cases
- 23:56Prioritizing tests using business requirements
- 26:42Testability and defect density
- 29:48Critical user flows
- 32:15Code commits for risk assessment
- 33:40Risk-based test plan matrix
- 37:09Unknown unknowns in testing
- 40:37Summary
- 43:01Q&A: Minimizing opinion in risk ratings
- 45:08Q&A: Schedule risks and testing
- 46:54Q&A: Tools for visualizing risks
- 47:37Q&A: Calculating risk exposure
- 48:39Q&A: When to start risk rating
- 49:40Q&A: Metrics for risk estimation
- 51:03Q&A: Risk detail level
related talks
40mRisk Based Testing in Agile Teams
46mInside Scoop on Risk-Based Testing
32mRisk-Based Test Effort Management
28mRisk Based Testing in Agile Teams
39mRisk-based testing in practice: how to work with it
39mHow to Talk about Coverage
35mRisk Based Code Coverage Analysis
01h 04mBuilding on Success, Beyond the Obvious