Test Driven Development (TDD) FAQs

Question 1

What is the 'Iron Law' of this TDD skill?

Accepted Answer

The Iron Law states that no production code should be written without a failing test existing first to prove the need for the code and provide evidence of its correctness.

Question 2

How does it handle cases where I don't know what to test?

Accepted Answer

The skill includes a 'When Stuck' guide that helps you identify the simplest possible test case or break down complex behaviors into smaller, testable units.

Question 3

What triggers the TDD skill in Claude Code?

Accepted Answer

The skill is triggered by phrases like 'tdd', 'test first', 'test driven', or 'red green refactor', and it is automatically active when OMC_TDD_MODE is enabled.

Question 4

Can I use this skill for fixing bugs?

Accepted Answer

Absolutely. The TDD methodology requires writing a test that reproduces the bug before implementing the fix, which ensures the bug is actually solved and prevents future regressions.

Question 5

How does the Red-Green-Refactor cycle work in this skill?

Accepted Answer

First, you write a failing test (Red). Second, you write the minimum code necessary to make that test pass (Green). Finally, you clean up the code without changing its behavior (Refactor).

Test Driven Development (TDD)

Key Features

Use Cases

Test Driven Development (TDD)

Key Features

Use Cases