What problem does it solve?
Red-Green-Refactor provides a disciplined TDD workflow that prevents regressions, proves bugs exist before changing production code, and guides minimal, test-driven feature delivery so teams avoid brittle tests and hidden defects.
Core Features & Use Cases
- Prove-before-change: Always start by writing a failing test that documents the expected behavior so fixes are auditable and reproducible.
- Minimal, safe fixes: Implement the smallest possible change to make the test pass, then refactor with strong test coverage to avoid introducing regressions.
- Team workflows: Supports splitting work into a failing-test commit and a separate fix commit for clearer reviews, and encourages hypothesis-driven investigations when root causes are unclear.
- Language guidance: Includes practical advice and examples for Rust, Go, TypeScript, and Solidity to apply the pattern in real projects.
Quick Start
Reproduce the failing behavior, write one failing test that asserts the correct public behavior, run the test to confirm failure, implement the minimal change to pass the test, and then refactor with tests remaining green.