gladius

Test-driven development requires writing a failing test before any production code to guide implementation and prevent regressions. It enforces a red-green-refactor cycle, driving small, testable increments by validating behavior first, then writing minimal code to pass.

Use test-driven development for bug fixes and refactoring by writing a failing test that reproduces the bug or validates the desired behavior change first. This ensures tests exist before modifying production code, guarding against regressions across the codebase.

Yes, test-driven development is applicable to creating new features and changing behavior across a codebase. It guides feature work by requiring a failing test before production code, validating behavior through small, testable increments.

Test-driven development discourages test-after coding by requiring a failing test before any production code is written. This approach validates behavior upfront and guides implementation, whereas writing tests afterward does not drive the design or enforce the red-green-refactor cycle.

Test-driven development may not suit tasks where behavior is difficult to validate through tests or where immediate, exploratory coding is required. It enforces a strict red-green-refactor cycle and discourages test-after coding, requiring a failing test before any production code.