Test-Driven Development FAQs

Question 1

Can I use this skill for fixing existing bugs?

Accepted Answer

Yes. The skill requires writing a failing test that reproduces the bug before any fix is implemented, ensuring the fix is verified and preventing future regressions.

Question 2

Why is 'Verify RED' mandatory?

Accepted Answer

Watching a test fail proves that the test is actually checking the intended behavior and is capable of catching a failure. If a test passes immediately, it isn't testing anything new.

Question 3

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

Accepted Answer

The Iron Law dictates that you must never write production code without a failing test first. If code is written before a test, it should be deleted and restarted using the TDD cycle.

Question 4

How does this skill handle refactoring?

Accepted Answer

Refactoring is only permitted after a 'Green' state is achieved. The skill ensures you clean up code while keeping tests passing, preventing functional changes during the cleanup phase.

Question 5

Are there any exceptions to using TDD with this skill?

Accepted Answer

Exceptions are rare and usually limited to throwaway prototypes, generated code, or configuration files, and typically require explicit confirmation from a human partner.

Test-Driven Development

主要功能

使用场景

Test-Driven Development

主要功能

使用场景