test-driven-development

Test-driven development is a coding methodology enforcing the Red-Green-Refactor cycle. It requires writing a failing test before implementation to verify behavior, prevent regressions, and improve code quality.

To start a new feature using TDD, first write a failing test that reflects the desired outcome. Then write the minimum implementation code to pass the test, and finally refactor the code while ensuring tests remain green.

You need to write a failing test before writing implementation code whenever starting any new feature, bug fix, or refactoring task. This ensures tests accurately verify desired behavior and prevent future regressions.

Yes, test-driven development is applicable to refactoring tasks. By ensuring existing tests pass before and after code modifications, you maintain code quality and prevent regressions during structural improvements.

Test-driven development requires a failing test first to guarantee the test actually verifies behavior and reflects the desired outcome. This principle prevents false positives and ensures code quality.

Enforcing the Red-Green-Refactor cycle strictly prohibits writing any production code without a failing test first. This limitation requires adherence to the methodology for all development, bug fixes, and refactoring tasks.