tdd-green-phase

To write minimal code for a failing unit test, implement only the smallest change required to turn the test green. This strict minimalism avoids feature creep and premature optimization during the TDD green phase.

The green phase in TDD is the stage where you implement minimal, focused code to make a failing test pass. It enforces safe progression from red to green by tackling one test at a time.

No, you should not optimize code during the TDD green phase. The workflow enforces strict minimalism with guardrails for quality, preventing premature optimization and extra behavior not demanded by the failing tests.

TDD green phase guidance recommends a one-test-at-a-time workflow. Tackling unit tests individually isolates code changes, reduces risk, and ensures safe progression from red to green with minimal implementation.

To avoid feature creep when implementing unit tests, use strict minimalism and propose only the simplest code change that satisfies the current failing test. Guardrails prevent adding extra behavior not demanded by tests.