test-driven-development

Test-driven development enforces writing a failing test before production code, implementing minimal logic to pass it, then refactoring for simplicity. This red-green-refactor cycle prevents regressions and ensures correct behavior across new features, bug fixes, and refactors.

Start by writing a failing test for the desired behavior, then implement the minimal code required to pass that test. This ensures new features, bug fixes, and refactors are covered by tests and promotes safe, incremental design and maintainable code.

Yes, test-driven development is applicable to bug fixes and refactors across typical development cycles. It requires a failing test to exist before production code changes, preventing regressions while guiding teams through the red-green-refactor loop for safe, incremental design.

Test-driven development prevents regressions by requiring tests before code. It enforces the red-green-refactor loop: write a failing test, implement minimal code to pass, then refactor to maintain simplicity and clarity, ensuring correct behavior throughout the development cycle.

Test-driven development enforces tests before production code, which may not suit exploratory prototyping where behavior is undefined. It requires a clear desired behavior to write a failing test first, making it less ideal for early-stage design exploration or throwaway code.