test-driven-development

Test-driven development is implemented by writing a failing test for the new behavior before any implementation code, then writing minimal code to pass, and finally refactoring to enforce the Red-Green-Refactor cycle.

The Red-Green-Refactor cycle in TDD is a strict methodology where you write a failing test, write minimal code to make it pass, and then refactor to ensure code quality and prevent regressions.

Bug fixes using strict TDD methodology require writing a test that fails and reproduces the bug before fixing the implementation code, ensuring the test verifies the intended outcome and prevents future regressions.

Test-driven development prevents code regressions in agile development by enforcing that tests are written first to verify specific behavior, actively discouraging bad practices and rationalizations for skipping tests.

Test-driven development should not be skipped during refactoring; it ensures code quality by verifying behavior through tests first, though it may require overcoming common rationalizations for not following the methodology.