Modern QA2026Applying Risk-Based Testing — tiles
Log inJoin
56 / 71 · 11 Manual Testing Fundamentals · Risk-Based Testing← prev⊞ allnext →☰ Read as one page

7.3Applying Risk-Based Testing

Step 1: List Feature Areas

Work with the product owner and developers to list every feature area being released or modified.

Step 2: Assess Risk

For each area, rate likelihood (Very Low / Low / Medium / High) and impact (Very Low / Low / Medium / High / Critical). Use the matrix above to determine overall risk level.

Step 3: Assign Test Depth

Risk Level Test Depth
Critical Exhaustive: all positive cases, all negative cases, edge cases, security, performance, cross-browser
High Thorough: all positive cases, key negative cases, boundary values, one cross-browser check
Medium Standard: happy path, key negative cases, one boundary check
Low Light: happy path only
Minimal Smoke: verify the feature loads and basic functionality works

Step 4: Prioritize Execution

Test critical and high-risk areas first. If time runs out, you have already covered the most important scenarios.