Sample report
The release decision, as a record you could defend
The record below was generated from the sample project built into AxonQA, by the same evaluation code that judges real releases. We are preparing to launch and have no customers to quote yet, so instead of a logo wall, here is the artifact itself. Every number came out of the product, not a copywriter.
The storefront, the team and the people named in it are fictional. The evaluation, the conditions and every figure are not.
This release declared automation and manual scope, so its bar carries no API row at all. A discipline the release was never judged against does not appear on its report.
Release 1.4
from Checkout hardening
- Assessment
- Frozen
- Environment
- staging
- Record
- RR-20260808-BFZL
Recorded readiness · Release 1.4 · staging
Ready to ship, with 2 things you are accepting.
Everything that must hold, holds. The rest were accepted by a person, with a reason. Judged against the project's bar as it stood when the report was made. Later changes to the bar do not change this record.
Evidence over time
Overview
- Release
- Release 1.4Sprint 24
- Plan
- Checkout hardeningstaging environment
- Frozen
- 8 Aug 2026, 00:23RR-20260808-BFZL
- Bar
- 9 conditionsin force for this release
- Checks
- 1613 automated · 3 manual
- Result
- 15 passed · 1 failedthe failure is accepted
- Coverage
- 100%of the release's stories
- Decision
- We shipped it8 Aug 2026, 00:53
Conditions assessed
All 9 configured conditions frozen into this assessment are listed below.
Must hold
5 of 5Any one of these failing means not ready. They cannot be accepted from inside the report.
Should hold
4 of 4Failing one of these does not stop a release. It has to be accepted by a person, on the record.
Failures and triage
Products page lists all available items
Failed in the sign-off run · dispositioned by Claire Bennett: Cosmetic, the badge catches up on the next interaction. · tracked as STORE-124, assigned to Marco Reyes
Triage annotates the record. It never changes the arithmetic: a dispositioned failure still counts against every condition that measures it.
Accepted, on the record
No unresolved requirement drift
The criteria changed wording only. Re-reviewed informally before sign-off.
Claire Bennett
7 Aug 2026, 22:53
Every failure has an owner
STORE-131 is parked for 1.5 and will be picked up with that release.
Claire Bennett
7 Aug 2026, 22:53
Evidence
| Evidence | Environment | Browser | Result | Ran | Build | Readiness use | Judged by | Tagged |
|---|---|---|---|---|---|---|---|---|
| Storefront E2EAutomation | staging | chromium | 13 / 13 | 1 Aug 2026 | Not recorded | 0 of 13 still current | Nothing. It sets no condition and no evidence age. | at run start · Claire Bennett |
| Storefront E2EAutomation | staging | firefox | 13 / 13 | 3 Aug 2026 | Not recorded | 0 of 13 still current | Nothing. It sets no condition and no evidence age. | at run start · Claire Bennett |
| Storefront E2EAutomation | staging | chromium | 13 / 13 | 4 Aug 2026 | Not recorded | 0 of 13 still current | Nothing. It sets no condition and no evidence age. | at run start · Claire Bennett |
| Sprint 24 sign-offAutomation | staging | chromium | 15 / 16 | 7 Aug 2026 | Not recorded | 16 of 16 still current | Manual and automation pass rate · No failure in tests at or above · Every failure has an owner · Every planned check produced a result · Evidence no older than | at run start · Claire Bennett |
The decision is recorded, never enforced. The report does not block a release; it makes sure nobody can later pretend the state of the evidence was different.
The bar fits the release
A release is judged only on the disciplines it declared. Each composition below is a real report you can open, generated from the same sample project.
Automation + manual + API
API checks fail for different reasons than the interface, so they carry their own condition. On this report the API pass rate joins the bar, judged from real API results.
View this compositionAutomation only
No manual phases were declared, so none can be outstanding, and the API condition is left off the bar entirely. The report never grows a row the release did not ask to be judged on.
View this compositionThe sample project is ready in every paid workspace. No sales call is required for Pro or Team.