tdd-workflows-tdd-green

Review the failing tests, identify the smallest change that satisfies the next assertion, and implement only that. Use techniques like Fake It (hard-coded returns), Obvious Implementation, or Triangulation, running tests after each change.

The green phase is the second step of the red-green-refactor cycle where you write just enough code to make failing tests pass. Correctness matters more than design quality; improvements are deferred to the refactor phase.

Use Fake It for the first test of a new feature, when dependencies are complex, or when the approach is uncertain. Switch to a real implementation once multiple tests reveal a pattern or faking becomes more complex than real code.

No, only add error handling if a test explicitly requires it. The green phase prioritizes minimal passing code; validation, edge cases, and robustness belong to later tests and the refactor phase.

Common anti-patterns include gold plating with unrequested features, premature design patterns, performance optimization without metrics, adding new tests mid-phase, and refactoring while implementing. Each adds complexity beyond what tests require.