Test-Driven Development (TDD) FAQs

Question 1

Why does this skill require watching a test fail?

Accepted Answer

Watching a test fail (the Red phase) confirms that the test is actually checking the intended logic. If a test passes immediately, it provides no proof that it is testing the new behavior correctly.

Question 2

When is it acceptable to skip TDD with this skill?

Accepted Answer

Exceptions are rare and usually limited to throwaway prototypes, purely generated code, or basic configuration files. In most development scenarios, TDD is considered mandatory.

Question 3

Can I use this skill for bug fixes?

Accepted Answer

Yes. When a bug is found, the skill requires writing a failing test that reproduces the bug before implementing the fix. This proves the fix works and prevents future regressions.

Question 4

How does this handle the refactoring process?

Accepted Answer

Refactoring is only permitted during the 'Refactor' phase after the code has passed the tests (the Green phase). This ensures you can clean up the code without changing its external behavior.

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 before a test, the instructions require deleting it and starting over to ensure the test truly verifies the behavior.

Test-Driven Development (TDD)

주요 기능

사용 사례

Test-Driven Development (TDD)

주요 기능

사용 사례