Backend Testing

Backend Testing

Use this skill as a packet-first backend testing router.

The job is not to dump boilerplate for every framework. The job is to:

1. classify the request into the right backend test packet,
2. pick the smallest credible mix of test layers,
3. make dependency realism and data control explicit,
4. split local vs PR vs slower lanes honestly,
5. route policy, contract-shape, and auth-implementation work away when they are the real task.

Read these when needed:

• references/intake-packets-and-route-outs.md
• references/test-layer-matrix.md
• references/stability-checklist.md

When to use this skill

• Add or repair backend coverage for APIs, services, repositories, workers, integrations, or auth flows
• Decide whether a backend change needs unit, integration, contract/API, or narrow smoke coverage
• Design fixture, factory, seed/reset, auth bootstrap, or environment-control strategy
• Decide when to use mocks, fakes, containers, or real dependencies
• Stabilize flaky backend suites, especially CI-only failures and local-vs-CI drift
• Review whether a backend suite is too broad, too slow, too mock-heavy, or missing a key layer