Skip to content
Sharan L · QA Engineering
Menu

← All case studies

QA Risk & Release Readiness Audit · Performance & Scalability Assessment · Accessibility

Release decision: from 14 defects to a clear Go/No-Go

Browser, accessibility and performance tests, combined with the API results, turned into a one-page release decision: v1.0 No-Go, v1.1 Go, with the reasons in business terms.

Demonstration on synthetic data in my own demo project, not client work.

Scenario

The same shop, the day before launch. The business is not asking "how many tests passed?" but "can we release, and what is the risk if we do?" The answer has to come from the test results, in a form a non-technical owner can sign off.

Risks

Tests

Defects found

IDDefectType
D14Customer name runs as code in the browser (stored XSS)High
D11"Place order" off-screen on phonesMedium
D12Unlabelled fields and low-contrast pricesMedium
D10Product list slows to ~1.5 s at 50 usersMedium
D04Tax truncated instead of roundedMedium

Evidence

Fix

Fixes verified in v1.1, then the report rebuilt from the new results. CI builds both reports on every run and fails unless v1.0 is No-Go and v1.1 is Go.

Result

v1.0
No-Go: 14 open defects (6 Critical or High), 3 of 18 requirements pass
v1.1
Go: 18 of 18 requirements pass, all 14 defects verified fixed
Speed at 50 users (95th percentile)
About 1.5 s on v1.0, about 3 ms on v1.1

Lessons

  1. Agree the verdict rules before testing starts, so the decision follows from the results and is not negotiated afterwards.
  2. Phone layout defects pass every desktop test: the hidden "Place order" button only appears at phone width.
  3. A speed number means little without a limit. 1.5 s only became a finding once 800 ms had been agreed as the target.

Need this for your product?

Get a suggested scope and starting price in four questions, or tell me about your project.

Scope BuilderGet a quote

Next case study: AI support features: a chatbot, a help-centre assistant and an order agent →