test-plan
Writes syntaxis/qa/test-plan.md: what gets tested, at which level, on what,
and when a cycle counts as done.
Invocation
Section titled “Invocation”/test-plan the whole plan/test-plan mobile narrow the pass to one sectionWhat it covers
Section titled “What it covers”Objectives, in scope, out of scope, test levels, environments, target devices and browsers, risk-based priority, entry and exit criteria, defect management, tooling, roles, and open questions.
What it guarantees
Section titled “What it guarantees”- It plans only for surfaces and tooling that exist or are explicitly planned.
- It never invents environments, devices, roles, or compliance requirements. A solo project with one environment says so.
- What is deliberately not tested gets recorded. An unstated gap is worse than a stated one.
- Exit criteria are never weakened to make a cycle pass. That call is yours.
- It writes no test cases and no test code.
See The QA Loop.