test-driven-development

The Red-Green-Refactor workflow in test-driven development is a cycle where you write a failing test, implement minimal code to pass it, and then refactor while keeping all tests green.

To safely refactor code without introducing regressions, use a test-first approach to establish passing tests, then modify the implementation while ensuring all tests remain green.

To start writing tests before implementing a new feature, encode the desired behavior into a failing test, implement just enough code to pass, and refactor the result.

Yes, you can apply test-driven development to both bug fixes and refactoring tasks by validating expected behavior with automated tests before and after making code changes.

Yes, you need automated tests to validate design when using a test-first approach, as they provide the essential feedback loop required for the Red-Green-Refactor cycle.