test-masterlisted

# Test Master ``` /\ /E2E\ <- Few (3-5 critical flows) /------\ /Integr.\ <- Some (all endpoints + DB) /----------\ / Unit \ <- Many (all business logic) /--------------\ / Smoke \ <- Minimal (1-2 basic tests) /------------------\ ``` ## Test Types — When to Use | Type | Use for | Written when | Details | |------|---------|-------------|---------| | **Smoke** | Framework configured, env vars, imports | Infrastructure setup (once) | [smoke-tests.md](references/smoke-tests.md) | | **Unit** | Business logic, decisions, transforms, error handling | Each task, immediately after code | [unit-tests.md](references/unit-tests.md) | | **Integration** | All API endpoints, DB ops, external services | End of feature (per Tech Spec) | [integration-tests.md](references/integration-tests.md) | | **E2E** | Top 3-5 critical flows, large features (>5 tasks) | After deploy to dev | [e2e-tests.md](references/e2e-tests.md) | Every API endpoint and DB write must have an integration test. For YES/NO criteria per type, see [decision-framework.md](references/decision-framework.md). ## Decision & Quality **Deciding what to test?** Read [decision-framework.md](references/decision-framework.md) — YES/NO criteria per type, E2E prioritization by project type, redundant testing anti-pattern. **Writing or reviewing tests?** Read [test-quality.md](references/test-quality.md) — good/bad test examples, mocking strategy per level. **Reviewi