test-quality-gatekeeperlisted

# Test Quality Gatekeeper Assess whether tests actually protect the system from regressions. Focus on real protection, not just coverage metrics. ## Core Principle :warning: **High coverage ≠ High protection.** A test suite with 90% coverage can still miss critical bugs if it only tests happy paths. ## When to Use - Reviewing test coverage for a feature - Evaluating test quality before release - Identifying gaps in regression protection - Assessing contract test coverage between services - Reviewing smart contract test completeness - Identifying flaky or unreliable tests ## Review Workflow On EVERY invocation, execute these steps: ### Step 1: Map Critical Paths Identify what MUST work for the system to be valuable: ``` Critical Paths: ├── Authentication flow (login, logout, session) ├── Core business logic (payments, trading, data processing) ├── Data integrity (writes, updates, deletes) ├── External integrations (APIs, webhooks, events) └── Error handling (failures, retries, recovery) ``` ### Step 2: Inventory Existing Tests ```bash # Find test files find . -name "*.test.ts" -o -name "*.spec.ts" -o -name "*_test.go" | head -50 # Count tests by type grep -r "describe\|it\|test(" --include="*.test.ts" | wc -l # Find test commands grep -E "test|jest|vitest|pytest|go test" package.json Makefile 2>/dev/null ``` Categorize tests: | Type | Count | Coverage | |------|-------|----------| | Unit tests | [count] | [what they cover] | | Integration tests | [count] | [what