Backend Testing

This is a backend test planning router, not a boilerplate generator. It takes vague requests like "we need API tests" and forces you to choose the smallest credible mix of unit, integration, contract, and smoke layers before writing code. It makes you decide up front whether to mock, fake, or containerize each dependency, how to seed and reset data, and which tests run locally versus in CI. The framework treats fixture strategy and flake stabilization as first-class design problems rather than afterthoughts. If you keep writing backend tests that are too slow, too brittle, or protecting the wrong risks, this will make you articulate the trade-offs before you commit.