1. Verdict and stamp
One plain sentence, such as “Your site has 3 problems to fix.”, and a rubber stamp: Issues found Acceptance incomplete or Selected checks passed.
Public explainer · illustrative sample
How to read a website QA release report
A report should show what was observed, what could not run, and what must be checked again. It should not turn incomplete coverage into a green release.
Anatomy of the certificate
Every Sybqa report opens as a one-page certificate. Five parts, top to bottom. Open the sample report to see them with a recorded example.
2. Scoreboard
Five counts: Failed, Blocked, Needs review, Not run and Passed. Only Passed counts as passed.
3. Fix these first
One tag per problem with the measured value, a screenshot, the steps to reproduce and a fix brief you can paste into an AI coding tool.
4. Not a pass yet
Blocked, Needs review and Not run items. None of them are shown as passed.
5. Hand it off
Save a PDF, copy a short summary, or download the data files.
Evidence states keep decisions honest
| Check | State | What evidence says | Release meaning |
|---|---|---|---|
| Visible labels on signup fields | Failed | Observed at a named route and viewport; screenshot and assertion belong in the report. | Fix before accepting this check. |
| Protected billing route | Blocked | Access or fixture was unavailable. No browser conclusion was recorded. | Blocked never means passed. |
| Mobile confirmation copy | Not run | Scope, time, or a prerequisite prevented execution. | Not run never means passed. |
| Button colour looks off | Dropped | Flagged by AI, then not confirmed by the browser. | Not an issue. It is listed so you can see what was checked. |
| Signup field fix | Recheck required | A proposed fix exists, but no matching assertion and captured evidence have confirmed it. | A recheck is required; a fix is never resolved by declaration. |
A useful report ties every claim to a boundary
Observed
Name target URL, route, viewport, assertion, and captured artifact. A failure is concrete enough to reproduce.
Coverage limit
Record the missing credential, inaccessible route, unavailable service, or unrun path. Keep its status visible beside passing work.
Recheck
Use the same route and assertion after a change. Mark it passed only when new evidence confirms the expected result.
Decision
State what was verified and what remains outside acceptance: deployed revision, external APIs, database writes, and protected journeys all need their own evidence.
Continue with a protected preview
When a release preview requires access, use a scoped test account and separate preview access from application login. The authenticated preview deployment testing guide gives a runnable local benchmark shape and its evidence boundaries.