TDD Integration Testing

Enforce strict Test-Driven Development using the Red-Green-Refactor cycle.

Mandatory Workflow

Every new feature MUST follow this strict 3-phase cycle. Do NOT skip phases.

Phase 1: RED – Write Failing Test

🔴 Write integration test that fails

Requirements:

• Feature requirement from user request
• Expected behavior to test

Deliverables:

• Test file path
• Failure output confirming test fails
• Summary of what the test verifies

Do NOT proceed to Green phase until test failure is confirmed.

Phase 2: GREEN – Make It Pass

🟢 Write minimal code to pass the test

Requirements:

• Test file path from RED phase
• Feature requirement context

Deliverables:

• Files modified
• Success output confirming test passes
• Implementation summary

Do NOT proceed to Refactor phase until test passes.

Phase 3: REFACTOR – Improve

🔵 Evaluate and improve code quality

Requirements:

• Test file path
• Implementation files from GREEN phase

Deliverables (either):

• Changes made + test success output, OR
• “No refactoring needed” with reasoning

Cycle complete when refactor phase returns.

Multiple Features

Complete the full cycle for EACH feature before starting the next:

Feature 1: 🔴 → 🟢 → 🔵 ✓ Feature 2: 🔴 → 🟢 → 🔵 ✓ Feature 3: 🔴 → 🟢 → 🔵 ✓

Phase Violations

Never:

• Write implementation before the test
• Proceed to Green without seeing Red fail
• Skip Refactor evaluation
• Start a new feature before completing the current cycle

Related Skills

• /mw-mr-mf – Make it Work/Right/Fast workflow that pairs with TDD
• /testing-best-practice – Testing philosophy for writing quality tests
• /plan-to-tasks – Convert plans to JSONL format with TDD-ready task structure