Test-Driven Development (TDD) FAQs

Question 1

Are there any exceptions to using TDD with this skill?

Accepted Answer

TDD is expected for all production code. Exceptions like throwaway prototypes or configuration files are only permitted after explicit consultation with a human partner.

Question 2

Why does the skill insist on watching a test fail?

Accepted Answer

Watching a test fail (the Red phase) is mandatory because it proves the test is actually checking the intended behavior and isn't passing accidentally due to existing code or incorrect test logic.

Question 3

How does this skill handle refactoring?

Accepted Answer

Refactoring is only permitted during the 'Refactor' phase of the cycle when all tests are Green. This ensures that code can be cleaned and optimized without changing its external behavior.

Question 4

Can I use this skill for bug fixes?

Accepted Answer

Yes. For bug fixes, the skill requires writing a failing test that reproduces the bug before any fix is implemented, ensuring the fix is verified and documented.

Question 5

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

Accepted Answer

The Iron Law mandates that no production code is written without a failing test first. If production code is written prematurely, the skill instructs the developer to delete it and start over from a test.

Test-Driven Development (TDD)

Key Features

Use Cases

Test-Driven Development (TDD)

Key Features

Use Cases