Skip to main content
Test Management

Risk-Based Testing

Prioritizing testing efforts based on the probability and impact of potential failures.

Full definition

Risk-based testing prioritizes test activities based on the risk of failure for each feature or component. It ensures that the most critical and risky areas receive the most testing attention.

Risk assessment formula: Risk = Probability of failure × Impact of failure

High risk (test more):

  • Core business flows (checkout, authentication)
  • Areas with complex logic
  • Recently changed code
  • Features with many integrations
  • Areas with a history of bugs

Low risk (test less):

  • Stable, unchanged code
  • Simple CRUD operations
  • Non-critical features
  • Well-tested components

Risk-based testing is especially important when:

  • Time is limited (every project, really)
  • Resources are constrained
  • You need to decide what to automate first
  • Prioritizing regression test suites

This approach is a key ISTQB concept and a skill that distinguishes experienced QA engineers from beginners.

Interview tip

When asked 'How would you test this feature with limited time?', the answer is risk-based testing. Identify the highest-risk areas and test those first.

Learn more about risk-based testing in practice

ISTQB track