Risk-Based Test Generator

Runs in browser Test Design

List features with probability and impact ratings and get a risk matrix, priority ordering, suggested depth of testing and test focus areas per feature.

Privacy: This tool runs entirely in your browser. Your input never leaves your device.

What is regression testing, and what does risk-based testing add?

Regression testing re-runs existing tests after a change to confirm that what used to work still does. Because a full suite grows beyond what any release window allows, risk-based testing ranks features by the likelihood and the cost of failure — payment, sign-in, data integrity first — and decides what runs on every build, what runs nightly and what is automated. A regression suite is the natural first target for automation.

Read the guide: How to Write Test Cases

How to use Risk-Based Test Generator

  1. List features as "Feature, likelihood, impact" with optional notes.
  2. Generate to see the ranked plan and the matrix.
  3. Copy the Markdown plan into your test strategy document.

Risk-Based Test Generator features

  • Likelihood × impact scoring on a 1–5 scale with Critical/High/Medium/Low levels
  • Accepts numbers or words (low, medium, high, likely, severe)
  • Prioritised plan with suggested test depth and focus areas per feature
  • 5×5 risk matrix with features placed in cells
  • Markdown plan and JSON export

Risk-Based Test Generator example

Prioritising three features

Input:

Checkout & payment, 4, 5
Search, 3, 3
Newsletter opt-in, 1, 1

Output:

1  Checkout & payment  4  5  20  Critical  Exhaustive: all techniques, automation, exploratory sessions…
2  Search              3  3  9   High      Thorough: full positive/negative/boundary coverage…
3  Newsletter opt-in   1  1  1   Low       Light: smoke test and one happy path

Frequently asked questions about Risk-Based Test Generator

How are features scored?

Score = likelihood × impact on a 1–5 scale. 15–25 is Critical, 9–14 High, 4–8 Medium, below 4 Low. Words such as low, medium, high, likely or severe are accepted as well as numbers.

What does "test depth" mean?

A recommended level of effort: exhaustive coverage with automation and exploratory sessions for Critical items, down to a smoke check for Low ones.

How do I estimate likelihood?

Consider recent changes, code complexity, defect history, new technology and developer experience. Impact reflects revenue, safety, legal and reputational damage if the feature fails.

Can I use the plan with a test management tool?

Export the prioritised table as CSV or the whole plan as Markdown/JSON and import it as your test-plan backbone.

References

  • ISTQB Certified Tester Foundation Level (CTFL) v4.0ISTQB · 2023The foundation syllabus of software testing: test levels and types, test design techniques, test management and tools.
  • ISTQB GlossaryISTQBThe standard definitions of testing terms — test case, regression testing, severity, priority, boundary value analysis and the rest.