What problem does it solve?
Prevents regressions and uncertainty by requiring reproducible failing tests before implementing or changing behavior, ensuring every change is verified and documented by the test suite.
Core Features & Use Cases
- Red‑Green‑Refactor cycle: Drive development by writing a failing test, implementing the minimal fix, then refactoring while keeping tests green.
- Prove‑It Pattern for bug fixes: Always reproduce reported bugs with a failing test before applying a fix to guarantee the issue is resolved and guarded against regressions.
- Test Pyramid guidance: Focus on fast, small unit tests supplemented by integration and E2E tests where appropriate; classify tests by size and resource usage.
- Browser testing advice: Combine TDD with runtime verification (DevTools inspection, screenshots, network checks) for UI bugs and end-to-end flows.
Quick Start
Write a failing reproduction test, run the test suite to confirm it fails, implement the minimal change until the test passes, then refactor while keeping tests green.