Reports and release readiness

A release decision backed by evidence, not a feeling

TestPlum's release readiness report turns recorded results into a ready or not-ready verdict using thresholds you set: at least one run in scope, minimum completion, minimum pass rate, no critical cases failing or blocked, a maximum number of open critical issues and a minimum share of passing requirements. Every check shows the numbers behind it.

TestPlum release readiness report with a not-ready verdict and six threshold checks

What you can do

Readiness verdicts, explainable risk scores, flaky-test detection, workload and a configurable report builder.

Readiness with explicit thresholds

Set the minimum pass rate, execution completion and requirement verification, and the maximum open critical issues. The verdict lists every check that failed and why.

Explainable risk-based selection

Each case gets a risk score from transparent rules: priority, a failed or blocked last result, edits since last execution, never executed, a failing requirement and flakiness. Start a run of the riskiest cases in one click.

Flaky test detection

A case is scored as flaky from how often its outcome flips between pass and fail across at least three decisive results.

Report builder

Build bar, line, pie and table reports from results, cases, runs and issues, per project or across the organization, and save them for the team.

Printable reports

Print or save as PDF a readiness report or a run report for sign-off meetings and audits.

How it works

  1. Set thresholds

    Agree the bar for release with your team once.

  2. Run your tests

    Results flow in from manual runs and CI.

  3. Read the verdict

    Every failing check links to the cases and issues behind it.

  4. Close the gaps

    Run the riskiest cases first, retest failures and re-check.

Reports and release readiness: frequently asked questions

How does TestPlum decide if a release is ready?

A release is ready only when every check passes: at least one run is in scope, completion and pass rate meet your thresholds, no critical-priority cases are failing or blocked, open critical issues are within your limit and enough requirements are passing with none failing.

How does TestPlum detect flaky tests?

For cases with at least three decisive results that include both passes and failures, the flaky score is the number of pass-to-fail or fail-to-pass flips divided by the number of decisive results minus one.

What is the risk score?

The risk score adds points for high priority (up to 40), a failed or blocked last result (35), edits since last execution (25), never executed (20), a failing linked requirement (15) and a flaky score of at least 0.3 (10). Higher scores are tested first.

See your release readiness in minutes

Create a workspace, add a project and record your first run. Everything on this site is in the product today.