Backend Test Plan

Core Workflow

1. Identify changed behavior, risk areas, data stores, external integrations, auth boundaries, and production impact.
2. Define coverage across unit, integration, contract, database/migration, authorization, error, performance, and regression tests.
3. Specify fixtures, test data, mocks/fakes, environments, and cleanup needs.
4. Tie each test to an acceptance criterion or failure mode.
5. Include non-happy paths: denied access, invalid input, dependency failure, concurrency, retries, and rollback.
6. Recommend what must pass before merge, release, or rollback.

Safety Rules