Test-Driven Development (TDD) Pro FAQs

Question 1

Can I use this skill for bug fixes?

Accepted Answer

Yes, the skill requires writing a test that reproduces the bug (Red phase) before implementing the fix (Green phase) to prove the fix works and prevent regressions.

Question 2

How does it handle testing anti-patterns like excessive mocking?

Accepted Answer

The skill encourages testing real behavior and using real code whenever possible, providing guidance to avoid mocking internal implementation details that make tests brittle.

Question 3

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

Accepted Answer

The Iron Law states that no production code may be written without a failing test first; any code written before the test must be deleted and restarted to ensure the test is actually verifying behavior.

Question 4

Does it support safe refactoring?

Accepted Answer

Absolutely. The skill guides you through the refactoring phase only after the code is 'Green,' ensuring you maintain passing status while cleaning up duplication and naming.

Question 5

When is it acceptable to skip the TDD process?

Accepted Answer

Exceptions are only recommended for throwaway prototypes, generated code, or configuration files, and usually require explicit permission from a human partner.

Test-Driven Development (TDD) Pro

주요 기능

사용 사례

Test-Driven Development (TDD) Pro

주요 기능

사용 사례