test-driven-development

Test-Driven Development improves software quality by guiding you through the Red-Green-Refactor cycle. You write a failing test first, implement the minimal code required to pass it, and then refactor to ensure robust functionality and maintainability.

The Red-Green-Refactor cycle is a core test-first development practice where you write a failing test, implement minimal code to make it pass, and then refactor. This iterative process ensures thorough testing and code reliability.

You should use TDD for new features, bug fixes, and refactoring efforts to ensure every function and method has corresponding tests. It maximizes code reliability by verifying correct functionality before implementation is complete.

You should not use Test-Driven Development when best practices indicate it is unsuitable, avoiding common anti-patterns. The Skill outlines specific scenarios where test-first approaches are unnecessary or counterproductive for your development context.

To avoid common anti-patterns in software testing, follow TDD best practices and debugging tips provided. This ensures your test-first approach maintains code quality without falling into typical testing traps.