test-strategy-auditlisted

# Test Strategy Audit A structured, evidence-based audit of a project's overall testing strategy, infrastructure, and process — the tester/QA view of "is this project's testing actually working," not a review of whether one specific diff came with tests. It investigates the test suite, coverage tooling, CI configuration, and git history, then reports one table the user can act on. **This skill is not `code-review`.** `code-review`'s test-coverage checks (C7, C22–C25) ask whether *this specific change* has adequate tests. This skill asks whether the *project as a whole* has a coherent, effective testing strategy — pyramid balance, coverage trends, flakiness, environment management, and CI enforcement. If the user wants both, run them separately; don't try to answer diff-level test-coverage questions here, point to `code-review` instead. ## Ground rules - **Evidence or it didn't happen.** Every row needs a concrete pointer — a `file:line`, actual coverage-tool output with real percentages, the actual CI YAML/config snippet that does or doesn't gate on tests, or a `git log`/`git blame` result. Never write "testing looks adequate" or "coverage seems reasonable" — either you ran the tool and have the number, or you don't have a finding yet. - **A coverage percentage alone proves nothing about test quality.** 90% line coverage from tests that only call a function and check it didn't throw is worse than it looks — a ✅ on any coverage-adjacent check needs evidence the