04 Release
Decide whether to ship from evidence, not a meeting
TestPlum turns recorded results into one release verdict: ready or not ready. The verdict comes from checks with thresholds you agree in advance, each pass counts by how much it really proves, and every failing check links to the place to resolve it. The portfolio shows the same verdict for every project.
What's included
A ready or not-ready verdict from agreed checks, a trusted pass rate, and verdicts for every project.
- 04.1
Checks you agree in advance
Runs in scope, execution completion, pass rate, trusted pass rate, critical tests failing or blocked, open critical bugs and requirements verified, each against a threshold you set.
- 04.2
A pass counts by what it proves
A pass with no assertions, a pass on retry, a flaky test, a test changed since it ran, an unreviewed AI-written test or a manual result without an expected outcome counts only partly.
- 04.3
Where to resolve each check
Every failing check links to where it is fixed: the open runs, the failures to sort, the open bugs, the coverage gaps or the weakest passes.
- 04.4
A report to sign
Print the verdict with its evidence and sign-off lines for the go or no-go meeting, scoped to all active runs, a cycle or one run.
- 04.5
Every project's verdict
The portfolio shows each project's verdict, pass rate and trusted pass rate side by side.
- 04.6
Insights behind the verdict
What to test next by risk, which tests are unstable, who is doing what, and custom reports of your own.
- 04.7
Alerts in Slack and Teams
Post to a channel when a run is signed off, when automated results include failures and when the verdict changes, with a link straight to the run or the release page.
Every project's verdict, side by side
In practice
How it goes
Agree the thresholds
Set the pass rate, completion, coverage and bug limits the release must meet.
Test
Runs, automation and CI fill in the evidence as results arrive.
Resolve what blocks
Follow each failing check to the runs, failures, bugs or coverage gaps behind it.
Decide
Ready or not ready, with the evidence printed and signed.
What is a trusted pass rate?
A pass rate where each pass counts by how much it proves. A pass with no assertions counts a tenth, a pass on retry or from a flaky test half, a pass from a test changed since it ran or an unreviewed AI-written test 60 percent, and a manual pass without an expected result 70 percent. A green suite of weak tests cannot make a release look ready.
Can I change the release thresholds?
Yes. The pass rate, trusted pass rate, completion, requirement coverage and open critical bug limits are set per verdict, and the scope can be all active runs, one cycle or one run.
Can the team hear when the verdict changes?
Yes. Connect a Slack or Microsoft Teams channel in project settings and choose its alerts: a run signed off, automated results with failures, or the release verdict changing. Each message links to the run or the release page.
Can I see the verdict for every project?
Yes. The portfolio lists every project you can see with its verdict, pass rate, trusted pass rate, open runs and open bugs.
The rest of the loop
Understand failures
Failures grouped by cause and sorted with reasons, one bug per cause, and fixes proven before approval.
Failures in detail 01 · TestsKnow what to test
Structured steps, versions, folders, templates, requirements coverage and imports from other tools.
Tests in detailRelated guides
What is test management?
Test management is how a team plans, writes, runs and reports on software tests. Learn the core building blocks, the metrics that matter and how to choose a tool.
Guide · 7 minRequirements traceability matrix: what it is and how to build one
A requirements traceability matrix maps each requirement to its tests, results and defects. The columns to include, a worked example and how to keep it current.
Guide · 7 minRelease readiness: six checks that tell you if a build can ship
A release readiness checklist for QA teams: scope, completion, pass rate, critical failures, open critical defects and verified requirements.
Guide · 7 minFlaky tests: how to detect, measure and fix them
A flaky test passes and fails without a relevant change. A simple formula to measure flakiness from test history, common root causes and a triage process that works.
Guide · 6 minRisk-based testing: prioritise the tests that matter most
Risk-based testing orders tests by the likelihood and impact of failure. A transparent scoring model built from priority, recent failures, changes and coverage gaps.
Find out whether your next release is ready
Create a workspace, import your tests or write a few, and record a run. Everything on this site is in the product today.