Test-Driven Development Workflow FAQs

Question 1

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

Accepted Answer

The Iron Law states that no production code can be written without a failing test first. If production code is written before a test, it must be deleted and restarted to ensure the test truly validates the behavior.

Question 2

Does this skill support refactoring?

Accepted Answer

Absolutely. It encourages refactoring only after reaching a 'Green' state (passing tests), allowing you to clean up code while the tests verify that behavior remains unchanged.

Question 3

Can I use this skill for bug fixes?

Accepted Answer

Yes, it is highly recommended for bug fixes. The skill requires writing a failing test that reproduces the bug before any fix is applied, proving the fix works and preventing future regressions.

Question 4

Are there any exceptions to using TDD with this skill?

Accepted Answer

Exceptions include throwaway prototypes, generated code, or configuration files. For all other production code, the skill enforces TDD unless otherwise directed by a human partner.

Question 5

Why does the skill insist on watching a test fail (RED phase)?

Accepted Answer

Watching a test fail proves that the test is actually checking the intended logic. If a test passes immediately, it might be testing the wrong thing or verifying existing behavior rather than the new requirement.

Test-Driven Development Workflow

主要功能

使用场景

Test-Driven Development Workflow

主要功能

使用场景