Test-Driven Development (TDD) Workflow FAQs

Question 1

Why does this skill insist on watching a test fail?

Accepted Answer

Watching a test fail (the Red stage) proves that the test is actually verifying the new behavior and isn't passing by accident or due to pre-existing code.

Question 2

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

Accepted Answer

The Iron Law dictates that no production code should be written without a failing test first. If code is written before a test, it must be deleted and restarted from a test-first approach.

Question 3

What happens during the Refactor stage?

Accepted Answer

During the Refactor stage, you clean up duplication, improve naming, and extract helpers while keeping the tests green. You do not add new features or behaviors during this phase.

Question 4

Can I use this skill for bug fixes?

Accepted Answer

Yes, it is highly recommended for bug fixes. You start by writing a test that reproduces the bug, verify it fails, and then implement the fix to make it pass.

Question 5

Are there any exceptions to using TDD with this skill?

Accepted Answer

Exceptions include throwaway prototypes, generated code, or configuration files, though you should generally consult with a human partner before skipping the TDD process.

Test-Driven Development (TDD) Workflow

Key Features

Use Cases

Test-Driven Development (TDD) Workflow

Key Features

Use Cases