4. Risk-based test selection
Test Automation · 48 pages source format
Pro automation is risk management with code. Learn to score features by impact × likelihood, map risks to layers, and say “no” to low-value checks with evidence.
What you'll learn
- Impact × likelihood scoring
- Revenue and trust paths first
- Automation ROI conversations with PMs
Build a risk matrix
List features. Score impact (1–5) and likelihood of failure (1–5). Multiply. High scores get automation priority.
Do this now
Score 8 features on Sauce Demo or a fictional SaaS. Automate the top 3 risks first on paper.
Trust paths vs edge cases
Login, pay, save data, permissions — automate early. Obscure edge cases may stay manual or get API-only checks.
Do this now
Identify 3 trust paths for any app you use daily. Write one automated check idea per path.
Say no with data
When stakeholders ask for “automate everything,” respond with pyramid, runtime, and flake cost — not opinion.
Do this now
Draft a 3-sentence reply to “Can we automate all 500 manual cases?”
Pro tip. Offer a smoke pack + quarterly expansion plan instead of a flat no.
Regression vs change detection
Regression proves old behavior still works. Change detection catches new bugs. Your suite mix should do both.
Do this now
Label your planned checks as regression or change-detection. Adjust if one type dominates.