dev-testing
Installation
SKILL.md
Testing & QA
Balance: ~40% Backend/API, ~40% Frontend/E2E (Playwright), ~20% Cross-cutting (CI, Security, TDD, Coverage) -- directional guidance, not a hard ratio.
Scope: test harnesses, fixtures, mock policy, runners, Playwright, CI gates, coverage. Root-cause analysis and debugging playbooks → dev-debugging.
This skill activates by change surface when work needs verification depth, regression coverage, or a reproducible test harness.
C0/C1 work (small local patches): See
dev§0.0 Work Classifier + §0.1 Patch Fast-Path before reading references.
Modular References
| File | When to Read | What It Covers |
|---|---|---|
references/core/crud-test-matrix.md |
When choosing verification depth for a classified task, or testing a CRUD slice | Risk-tier minimums, per-operation negatives, UI smoke rule |
references/edge-first-testing.md |
New unit/service/integration tests for features (skip for regression/contract tests) | Edge-first principle, test order by change type, 11-class edge matrix |
references/backend-testing.md |
Backend/API testing | Supertest patterns, DB fixtures, auth mocking |
references/ci-pipeline.md |
CI configuration | GitHub Actions, gates, caching, parallelism |
references/load-testing.md |
Performance/load testing, C3+ production readiness | k6/Locust, test types, measure→profile→verify, CI gates |
references/ml-evaluation.md |
ML model/LLM evaluation, quality gates | LLM-as-judge, RAGAS, DeepEval, CI eval gate, regression detection. CI eval gates are dataset-versioned + regression-based: pin prompts/models/retrieval config, preserve traces, calibrate judges on golden examples, fail only on meaningful regressions or safety failures |