QA Test Strategy and Coverage
Overview
Provide an evidence-first contract for risk-based QA strategy, coverage matrix, unit, integration, gameplay, platform, regression, automation, ownership, and exit criteria.
When to use
Use only for the trigger conditions in the description and when the requested artifact needs explicit owners, evidence, limitations, and verification.
When NOT to use
Do not use to summarize one playtest or merely run an existing test command.
Required inputs and context discovery
Collect exact project and build identity, requested scope, owners, dependencies, constraints, existing evidence, commands, artifact paths, risks, approvals, rollback or recovery, and unavailable information.
Safety and risk level
Risk level is read-only. Read-only review never authorizes mutation. Any load, rollout, publication, service, database, credential, or external-system action requires explicit human approval and bounded stop conditions.
Workflow
- Define scope, quality risks, supported platforms, environments, and release gates.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Map risks to unit, integration, gameplay, network, data, performance, security, and compatibility coverage.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Assign owners, fixtures, automation candidates, evidence artifacts, and triage policy.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Define regression selection, entry criteria, exit criteria, waivers, and BLOCKED handling.
Completion criterion: evidence is recorded and unresolved items are explicit.
- Publish gaps and a prioritized implementation roadmap without inventing coverage.
Completion criterion: evidence is recorded and unresolved items are explicit.
Evidence and output contract
Produce qa-strategy.json with scope, snapshot, findings, owners, commands and exit codes, artifacts, acceptance criteria, Verified facts, Snapshot assumptions, Unverified hypotheses, BLOCKED items, and next actions.
Handoff contract
Record repository and path, goal, owned scope, do-not-touch scope, decisions, files changed, commands, exit codes, artifacts, restore information, blockers, next owner, and reactivation prompt.
Pitfalls and anti-rationalization
- Missing evidence is
BLOCKED, never PASS.
- A plan or review does not authorize production execution.
- Compile success, screenshots, or anecdotes do not prove broader coverage.
- Preserve unrelated work and generated-source ownership.
Verification checklist
References and scripts
No bundled runtime helper is required. Use project-owned plans, evidence, runbooks, schemas, and validation commands; repository governance tools remain full-clone-only.
1---2name: qa-test-strategy-and-coverage3description: Use when a game project, milestone, or feature needs a QA test strategy and coverage matrix across risk, test levels, platforms, environments, ownership, automation, regression, evidence, and exit criteria; not for one playtest session.4license: MIT5---6# QA Test Strategy and Coverage78## Overview9Provide an evidence-first contract for risk-based QA strategy, coverage matrix, unit, integration, gameplay, platform, regression, automation, ownership, and exit criteria.1011## When to use12Use only for the trigger conditions in the description and when the requested artifact needs explicit owners, evidence, limitations, and verification.1314## When NOT to use15Do not use to summarize one playtest or merely run an existing test command.1617## Required inputs and context discovery18Collect exact project and build identity, requested scope, owners, dependencies, constraints, existing evidence, commands, artifact paths, risks, approvals, rollback or recovery, and unavailable information.1920## Safety and risk level21Risk level is `read-only`. Read-only review never authorizes mutation. Any load, rollout, publication, service, database, credential, or external-system action requires explicit human approval and bounded stop conditions.2223## Workflow241. Define scope, quality risks, supported platforms, environments, and release gates.25 Completion criterion: evidence is recorded and unresolved items are explicit.262. Map risks to unit, integration, gameplay, network, data, performance, security, and compatibility coverage.27 Completion criterion: evidence is recorded and unresolved items are explicit.283. Assign owners, fixtures, automation candidates, evidence artifacts, and triage policy.29 Completion criterion: evidence is recorded and unresolved items are explicit.304. Define regression selection, entry criteria, exit criteria, waivers, and BLOCKED handling.31 Completion criterion: evidence is recorded and unresolved items are explicit.325. Publish gaps and a prioritized implementation roadmap without inventing coverage.33 Completion criterion: evidence is recorded and unresolved items are explicit.3435## Evidence and output contract36Produce `qa-strategy.json` with scope, snapshot, findings, owners, commands and exit codes, artifacts, acceptance criteria, Verified facts, Snapshot assumptions, Unverified hypotheses, BLOCKED items, and next actions.3738## Handoff contract39Record repository and path, goal, owned scope, do-not-touch scope, decisions, files changed, commands, exit codes, artifacts, restore information, blockers, next owner, and reactivation prompt.4041## Pitfalls and anti-rationalization42- Missing evidence is `BLOCKED`, never PASS.43- A plan or review does not authorize production execution.44- Compile success, screenshots, or anecdotes do not prove broader coverage.45- Preserve unrelated work and generated-source ownership.4647## Verification checklist48- [ ] Scope, identity, owners, and exclusions are explicit.49- [ ] Every verdict cites observed evidence or is labeled Unverified/BLOCKED.50- [ ] Risks have mitigations, triggers, owners, and dates.51- [ ] No unauthorized mutation, publication, deployment, or destructive action occurred.52- [ ] Handoff names the next bounded action.5354## References and scripts55No bundled runtime helper is required. Use project-owned plans, evidence, runbooks, schemas, and validation commands; repository governance tools remain full-clone-only.
hoatv2211