backend-test
Installation
SKILL.md
Backend Test
Give the project a test suite that catches real regressions, runs safely, and reports honest results.
When to Use
- The user wants tests written, run, expanded, or repaired, or asks about coverage or test strategy.
- A feature, auth change, or refactor needs tests (new tests, a negative-test matrix, or a baseline).
backend-debugasks for a failing test that reproduces a bug.- Tests are failing, slow, flaky, or missing, or a test framework must be chosen.
Not for: fixing production bugs (backend-debug), building features (backend-implement), behavior-preserving restructuring (backend-refactor), or execution-based health checks (backend-doctor). backend-test writes and changes test code, test config and fixtures only.
Before You Start
- Resolve the shared docs folder (""): first
_shared/inside this skill's folder (bundled installs), then../_shared/next to it; other fallbacks are in<shared>/context-loading.md-> Resolving_shared/Files. A missing shared doc is a warning, not a stop. - Read
<shared>/tool-rules.md(mode=auto contract, Production Targets, Test Integrity, Command Time Budgets, checkpoints) and<shared>/host-tools.mdif the actions below don't map clearly to your host's tools. Read<shared>/memory-schema.md-> test-strategy.md before writing that file. - Load project memory per
<shared>/context-loading.md: priorities 1-2 always, 6 (test-strategy.md) always, 3 (db-schema.md) for integration tests, 4 (api-patterns.md) for endpoint or contract tests, andissues.mdfor intents repair and reproduce. If memory is missing, runbackend-scanfirst when possible; otherwise continue from the manifests and say so in the summary. - If the detected stack matches a file in
<shared>/stacks/, read it (its Testing and Local and Test Setup sections in particular).