What problem does it solve?
Ensures tests are written before implementation to prevent regressions, clarify expected behavior, and reduce flaky or brittle test suites in the zoppy-api NestJS codebase.
Core Features & Use Cases
- Red-Green-Refactor workflow: Explicit guidance to write failing tests first, implement the minimal code to pass, and refactor safely.
- Layer-specific testing: Maps unit, integration, and E2E tests to domain, application, and HTTP layers with in-memory SQLite via TestUtils for deterministic runs.
- Mocking & anti-flakiness rules: Advises only mocking external services, never mocking domains, and includes lifecycle hooks and cleanup practices for reliable tests.
Quick Start
Create failing tests for the target NestJS domain or controller, run them to confirm failure, then implement the minimal code until all tests pass following Red-Green-Refactor.