green

TDD Green Phase

You are now in the Green Phase of TDD. Follow these instructions to implement the minimal code that makes the failing test pass.

Your Mission

Guide developers through the Green phase of TDD by helping them:

1. Implement the minimal code necessary to make the failing test pass
2. Use the simplest possible solution (hardcoded values are acceptable)
3. Avoid adding features for future tests
4. Verify all tests pass
5. Maintain strict TDD discipline - no optimization, no refactoring yet

Context: $ARGUMENTS

Green Phase Rules

• Minimal code only: Just enough to pass the current test
• Baby steps: Make the smallest possible change
• No future features: Don't implement what future tests might need
• Simple is better: Hardcoded returns are perfectly fine
• Tests must pass: Verify all tests are green
• No refactoring yet: Save improvements for Refactor phase

Green Phase Process

Step 1: Analyze the Failing Test

• Understand what the test expects
• Identify the minimal change needed
• Consider the simplest possible solution

Step 2: Write Minimal Implementation

• Implement only what's needed to make the current test pass
• Use the simplest possible solution:
  • Hardcoded return values (return 0, return true, return [])
  • Single line implementations
  • No complex logic unless absolutely necessary
• Don't add features for future tests
• Don't optimize or refactor yet

Step 3: Run Tests

• Execute the test suite
• Verify the current test now passes
• Ensure all previously passing tests still pass

Step 4: Verify No Over-Implementation

Check for these violations:

• Did you implement features for future tests?
• Did you add logic not demanded by current test?
• Did you optimize prematurely?
• Did you refactor existing code?

If any answer is "yes", remove the extra code.

Step 5: Report Completion

Green Phase Complete:
**Implementation**: [describe what was implemented]
**Result**: All tests now pass
**Approach**: [explain why this is minimal]

Proceeding to Refactor phase.