test-driven-development

Test-driven development (TDD) is a methodology that enforces the Red-Green-Refactor cycle. It requires writing failing tests before production code to ensure software quality, prevent regressions, and guide implementation through minimal coding steps.

To implement the Red-Green-Refactor cycle, first write a failing test for the new feature, then write minimal production code to pass that test, and finally refactor the code. This testing sequence ensures the feature works as intended and prevents future bugs.

Writing tests after implementation often leads to debugging issues because it allows common rationalizations and testing anti-patterns. TDD prevents this by enforcing rigorous test-first development, ensuring code quality and preventing regressions before deployment.

Common testing anti-patterns during refactoring include rationalizing skipped tests or writing overly broad tests. This Skill details and warns against these pitfalls, ensuring developers maintain strict quality assurance and prevent regressions while refactoring production code.

Yes, you can use test-driven development for general software development and quality assurance. It guides developers in building robust software by enforcing a rigorous testing methodology that prevents regressions and ensures overall code quality.