Release Verdict & Quality Gate
What It Does
Release decisions usually mean reading several reports and asking around: did the tests pass for the right reasons, are there open security findings, did the load test meet its targets, did anyone review the breaking change? The release verdict joins those answers into one per API and environment, with the reasons listed and each one linked to its evidence. Because the verdict is categorical, nobody has to guess what a score of 82 means. Because missing evidence is "no evidence yet" rather than a pass, an API nobody tested cannot slip through as green. Release managers see the verdict on the API page, pipelines gate on it, and auditors get a record of what was judged, by which policy, and who asked.
Overview
A test report tells you what passed. A release verdict tells you whether to ship. For each API, or for a whole project in a given environment, Shift-Left API returns one of four answers: ready, ready with risks, not ready, or no evidence yet. Each reason links to the evidence behind it. The verdict is computed from what the platform already records: functional results and their failure causes, open security findings, performance targets, breaking changes waiting for review and accepted risks. The worst result wins, and missing evidence never counts as a pass. A failure that analysis puts down to the environment or test data counts as missing evidence, not as a failing API. A suspected product bug blocks the release.
Key Capabilities
How It Works
- 1
Set the project's release policy: for example, no open critical or high security finding without an accepted risk, and no suspected product bug
- 2
Run your tests, load tests and security checks as usual; nothing extra is generated or run to build the verdict
- 3
Open an API, or the project's API list, to see its verdict and the reasons behind it
- 4
Keep the verdict as a record when it matters, or let the CI pipeline record it with the build number
- 5
Gate the release in GitHub Actions, GitLab CI, Azure DevOps or Jenkins on the verdict, with an optional pull request comment
Available on
professional Plan & Above
Upgrade to the professional plan to unlock this feature.
Documentation
Step-by-step guides for setting up and using Release Verdict.
- Release Verdict: Is This API Ready to Release?One answer per API or project, ready, ready with risks, not ready or no evidence yet, with every reason linked to the evidence behind it.
- Run Triage: Understand Why a Run FailedWhen a run of 200 tests ends with 47 failures, the hard part is not fixing them. It is working out how many different problems those 47 failures actually are.
- CI/CD: Run Test Packs from GitHub ActionsRun a Shift-Left API test pack in a GitHub Actions workflow with the first-party action, gate the build on its pass rate, and publish the JUnit results.
Go deeper
Guides and playbooks that show this capability in practice.
Try Release Verdict Today
Start your 15-day free trial — no credit card required.