QA regression report · sample
A generic example of the report you get after the build phase, on every run. It shows what was tested, what the outcome means, and which regressions were caught. Readable for non-technical people, also as Excel.
24
Test cases
21
OK
1
Regression
1
Known exc.
1
Out of scope
// results (selection)
| ID | Area | Test scenario | Outcome | Evidence |
|---|---|---|---|---|
| HOM.01 | HOM | Homepage loads, title + H1 present | OK | 2 |
| NAV.01 | NAV | Main navigation + proper 404 | OK | 2 |
| ZOE.01 | ZOE | Search: filter and sort | OK | 1 |
| CHK.01 | CHK | Checkout: pay with iDEAL | OK | 3 |
| CHK.02 | CHK | Checkout: apply discount code (total drops) | REGRESSION | 3 |
| LOG.01 | LOG | Login: existing customer | OK | 1 |
| REG.01 | REG | Signup: new account + verification email | OK | 2 |
| ACC.01 | ACC | Account: change and save details | OK | 1 |
| PRD.01 | PRD | Product page: price, variants, add to cart | OK | 1 |
| FORM.01 | FORM | Contact form: validation + submit | OK | 2 |
| LNK.01 | LNK | Internal links return no errors (< 400) | OK | 1 |
| LNK.05 | LNK | External partner link (rate-limited) | KNOWN EXCEPTION | 1 |
| SEO.01 | SEO | Title, meta description, canonical | OK | 1 |
| TOE.01 | TOE | A11y smoke: exactly 1 H1 and html[lang] | OK | 1 |
| PDF.01 | Terms PDFs: 200 + application/pdf | OK | 1 | |
| MOB.02 | MOB | Mobile checkout (small screen) | OUT OF SCOPE | 0 |
// what does a red result mean?
CHK.02 · REGRESSION. The discount code is accepted, but the order total does not change. Caught on acceptance, before production. Evidence: 3 screenshots (input, confirmation, order total). A new failure since the last green run, so worth picking up.
LNK.05 · known exception. An external partner link sometimes returns a rate limit (429). Documented as a known exception, does not count as a regression.
LNK.05 · known exception. An external partner link sometimes returns a rate limit (429). Documented as a known exception, does not count as a regression.
// the principle
Every test case verifies the outcome, not just that an action was performed (order total drops, step reached, link status < 400). So red really means something. Not hundreds of meaningless tests, but a reliable safety net on what matters.