Skip to content
Sharan L · QA Engineering
Menu

Go/No-Go release report

This is what you receive at the end of an engagement: a release decision you can act on, written for product owners and CTOs — not a list of test IDs. Both samples below were generated automatically from real runs against ShopLab.

ShopLab v1.0 · seeded defects

No-Go

  • 14 open defects, 6 of them Critical or High
  • 3 of 18 requirements pass; 7 of 7 business risks open
  • p95 ≈ 1.5 s at 50 users (target 800 ms)
Download the PDF (5 pages)

ShopLab v1.1 · fixed

Go

  • 18 of 18 requirements pass; all 14 defects verified fixed
  • All 7 business risks mitigated; 4 residual risks named with mitigations
  • p95 ≈ 3 ms at 50 users
Download the PDF (4 pages)

What the report contains

  • Verdict and the reasons behind it
  • Executive summary in business language
  • Open defects with business impact and evidence
  • Business risk register (impact × likelihood)
  • Requirements traceability (18 requirements → tests)
  • Performance, test execution and verified fixes
  • Residual risks with recommended mitigations

Published verdict rules

No-Go
Any open Critical or High defect, or a failing performance or security requirement.
Go with risks
Only Medium or Low defects open, each with a mitigation.
Go
No open defects above Low and every requirement passes.

The rules are code with their own unit tests, and CI fails unless v1.0 is No-Go and v1.1 is Go.