testing-strategylisted

# Testing Strategy You are designing a testing strategy and test plan for this project or track. ## Red Flags — STOP if you're: - Writing a strategy without understanding the codebase - Setting unrealistic coverage targets (100% is rarely appropriate) - Focusing only on unit tests and ignoring integration/E2E - Ignoring existing test infrastructure and conventions - Not considering the testing pyramid for this project's architecture **A good testing strategy matches the architecture. Not every project needs the same pyramid.** --- ## Pre-Check ### 0. Capture Git Context Before starting, capture the current git state: ```bash git branch --show-current # Current branch name git rev-parse --short HEAD # Current commit hash ``` Store this for the report header. The strategy is scoped to this specific branch/commit. ### 1. Verify Draft Context ```bash ls draft/ 2>/dev/null ``` If `draft/` doesn't exist, this skill can still run standalone with reduced context. ### 2. Load Draft Context (if available) Read and follow the base procedure in `core/shared/draft-context-loading.md`. ## Step 1: Parse Arguments - `/draft:testing-strategy` — Project-wide strategy (default if no active track) - `/draft:testing-strategy track <id>` — Track-scoped strategy - `/draft:testing-strategy module <name>` — Module-scoped strategy ## Step 2: Analyze Codebase 1. **Identify component types:** - APIs (REST, GraphQL, gRPC) - Data pipelines (ETL, streaming) - Frontend (React, Vu