tdd-mastery

Test-driven development begins by writing a failing test first, then implementing minimal code to pass it. This Skill enforces the Red-Green-Refactor cycle, guiding you through each step to ensure robust, well-tested functional logic implementations.

The Red-Green-Refactor cycle mandates writing a failing test, writing minimal code to pass it, and then refactoring with tests as a safety net. This methodology ensures code quality and prevents regressions during business logic implementation.

To enforce minimum test coverage thresholds, this Skill mandates target coverage levels and provides checklists for writing effective tests. It uses the refactoring phase to improve code quality while maintaining a safety net of passing tests.

For structuring TDD tests, you should use the Arrange-Act-Assert and Given-When-Then patterns. This Skill provides these specific patterns to standardize test quality and ensure clear validation of business and functional logic.

You should use test-driven development when implementing new business or functional logic to ensure robustness. By writing tests before the implementation, you validate requirements upfront and build a safety net for future refactoring.

Test-driven development works for refactoring existing code by using passing tests as a safety net. This Skill guides you through the refactoring phase to improve code quality while ensuring the functional logic remains validated.