test-plan-design
How to design a test plan — scope and risk-based prioritization, the test pyramid, case-design techniques (equivalence partitioning, boundary values, decision tables), entry/exit criteria, coverage and requirement traceability, test data and environments. Deep reference with a runnable coverage-gap check.
Free & open source (Apache-2.0) — view the source on GitHub.
Overview
A test plan is a budget: finite effort spent where it prevents the most expensive failures. The goal is never "test everything" — that is impossible and economically illiterate. The goal is to make a defensible decision about *what* to test, *at which layer*, *with which cases*, and *when you are done*. This skill is the deep reference for that decision. Heavy detail lives in references/; copy-pas
What it covers
- Scope and risk-based prioritization
- The test pyramid — choosing a layer
- Case-design techniques
- Entry and exit criteria
- Coverage and traceability to requirements
- Test data and environments