tdd-fieldguide

To start test-driven development, follow the Red-Green-Refactor cycle: write a failing test first, implement the minimum code to make it pass, then refactor systematically to ensure high code quality and maintainability.

The Red-Green-Refactor cycle is a TDD methodology where you write a failing test, implement the minimum code to pass the test, and then systematically refactor the implementation to improve code quality without changing behavior.

Yes, this TDD workflow supports both TypeScript/Bun and Rust development environments, providing language-agnostic guidelines and examples to enforce disciplined testing practices across different tech stacks.

To fix bugs using a test-first approach, write a failing test that reproduces the specific bug, implement the fix to make the test pass, and then refactor the code to ensure structured workflow management and prevent regressions.

During refactoring, you should track code quality metrics such as code coverage, mutation testing, and test performance to ensure your test suite remains robust and your implementation maintains high quality standards.

You should avoid writing tests before implementation code only if you are doing rapid prototyping without clear requirements; otherwise, disciplined test-first workflows are enforced for both new features and bug fixes to guarantee maintainability.