🧪 QA & Testing · Test Strategy
Prioritize testing by risk, not habit
Failure likelihood × impact matrix focusing effort where bugs hurt most.
intermediate~25 minQA EngineersSDETsTest Automation Engineers
Steps
- 1List modules; score failure probability from change frequency + complexity
- 2Score business impact: money paths, data integrity, legal exposure first
- 3Matrix top-right quadrant gets deepest coverage and fastest fixes
- 4New features inherit high risk scores until proven stable
- 5Revisit after every incident; incidents reveal mis-scored areas
- 6Publish the matrix so devs understand review depth expectations
Common Pitfalls
- ▲Equal test depth everywhere = shallow where it matters
- ▲Legacy untouched code tested ritually
Commands
Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill test-strategy-risk-based-testingInstall globally
$ npx skills add aniruddhaadak80/skills --skill test-strategy-risk-based-testing -gTags
#risk#prioritization#qa#qa-testing#test-strategy