QA Deliverable Checklist

---
name: QA Deliverable Checklist
description: Hit every literal requirement a QA deliverable/grade checks for.
---
# QA Deliverable Checklist

QA deliverables (test plans, bug reports, automation strategies) are graded on coverage of required test categories, cases, and process definitions. Run this checklist before submitting.

## Universal checks
- **Named addressee** if the brief implies one.
- **Word count** inside any band.
- **Labeled sections** using the brief's exact names.

## Test plan specific
- **Scope**: state what's IN test AND explicitly what's OUT.
- **Test categories** — include ALL of: happy path, input validation, boundary cases, error/negative cases, cross-device/responsive, accessibility, performance (if applicable). The brief enumerates required categories; reproduce each.
- **Specific cases** under each category — name the concrete scenario (invalid email, weak password, mismatched passwords, unchecked required box).
- **Entry criteria** (when testing starts) and **exit criteria** (when it ends) — state both explicitly.
- **Bug reporting**: required fields (title, steps to reproduce, expected/actual, environment, evidence, severity, priority).
- **Triage**: distinguish severity (how bad) from priority (how soon); define the decision outcomes (fix now / defer / reject).

## Bug report specific
- Title is one searchable line summarizing the symptom.
- Steps numbered, exact, from a known state.
- Expected vs actual stated.
- Environment specifics (browser/OS/build/role).
- Evidence attached (screenshot/video/stack trace).

## Automation specific
- Pyramid: many unit, some integration, few e2e.
- Automate stable behavior; keep humans on exploratory.

## Final pass
Re-read the brief; tick each required category and case. QA rubrics reward exhaustive category coverage — a missing category (e.g. forgetting responsive checks) loses all its points.