tdd

Test-Driven Development requires following the RED-GREEN-REFACTOR cycle. You write a failing test first, implement the minimum code to pass that test, then refactor for clarity and improvements. This workflow ensures all code changes are driven by failing tests.

The RED-GREEN-REFACTOR cycle is a development workflow where you write a failing test first (RED), implement minimal code to pass the test (GREEN), and then refactor the code for improvements (REFACTOR). This methodology leads to robust software.

To verify 100% test coverage during Test-Driven Development, you must run coverage verification tools after implementing code changes. This Skill mandates strict coverage verification to ensure every code modification is fully backed by passing tests.

Yes, Test-Driven Development enforces adherence to conventional commit messages and pull request requirements. Following these standards ensures that all code modifications, including refactoring, are properly documented and reviewed.

Test-Driven Development should be used for refactoring when you need to improve code quality and maintainability. By writing failing tests before modifying the code, you ensure the refactoring process does not break existing functionality and maintains high coverage.

The best way to maintain code quality is enforcing a Test-Driven Development workflow. By driving all code modifications through failing tests and verifying 100% coverage, you achieve more robust and maintainable software.