tdd-workflows-tdd-green

To fix failing tests in TDD, you identify the failing behavior and apply the smallest deterministic code change required to move the suite from red to green. This keeps changes intentionally minimal and scoped only to the failing behavior.

The TDD green phase is the process of applying the smallest possible code change to pass the next failing test. You implement a minimal inline change, run the suite to confirm progress, and iterate one failing test at a time.

When applying minimal fixes to pass tests, you document shortcuts and technical debt for the refactor phase. This maintains long-term clarity by staging refinement to extract cleaner layers only when needed later.

No, you keep changes scoped strictly to the failing behavior when fixing a failing test suite. Modifying existing passing tests is avoided to ensure the minimal fix remains deterministic and focused.

The best way to iterate through multiple failing tests is to apply the smallest fix for one failing test at a time. Run the test suite after each individual change to confirm progress and maintain deterministic scope.