Test-Driven Development (TDD) FAQs

Question 1

Why is watching a test fail (Verify RED) mandatory?

Accepted Answer

If you don't watch the test fail, you cannot be certain that the test is actually testing the new behavior or if it is passing by accident due to unrelated code or environmental factors.

Question 2

Can I keep code I wrote before a test as a reference?

Accepted Answer

No. According to this skill's strict discipline, any code written before a test must be deleted to ensure the implementation is truly driven by the tests and not by pre-existing implementation bias.

Question 3

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

Accepted Answer

The Iron Law dictates that no production code should be written without first having a failing test that verifies the intended behavior. If code is written before a test, it must be deleted and rewritten.

Question 4

How does this skill handle bug fixes?

Accepted Answer

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

Question 5

When should I skip TDD using this skill?

Accepted Answer

TDD should be used for all new features, bug fixes, and refactoring. Exceptions are only permitted for throwaway prototypes, generated code, or configuration files after consulting a human partner.

Test-Driven Development (TDD)

주요 기능

사용 사례

Test-Driven Development (TDD)

주요 기능

사용 사례