skill-tdd

Test-driven development (TDD) is a software engineering workflow that enforces a red-green-refactor cycle, requiring engineers to write a failing test first before iteratively implementing minimal code to pass it.

To start test-driven development, write a failing test for the desired feature behavior, then implement the minimal code changes required to pass that test, and repeat the cycle until the entire feature is covered.

Yes, test-driven development applies to feature development, bug fixes, and refactoring across diverse technology stacks, guiding engineers to maintain a green test suite through continuous verification.

The best way to enforce a red-green-refactor cycle is by mandating a failing test before any implementation, writing minimal code to pass it, and continuously verifying the suite stays green to sustain long-term code quality.

Writing minimal code to pass tests improves code quality by forcing a tests-first approach that reduces the risk of defects and ensures continuous verification keeps the test suite green during feature development and refactoring.

A tests-first approach is not suitable when you cannot define clear expected behaviors upfront or when rapid prototyping requires immediate exploratory code before any continuous verification or test suite structure exists.