Test-Driven Development (TDD) FAQs

Question 1

Can I use mocks with this TDD skill?

Accepted Answer

The skill encourages testing real behavior with real code whenever possible. Mocks should only be used when dependencies are unavoidable or external services are involved.

Question 2

How does the Red-Green-Refactor cycle work here?

Accepted Answer

First, you write a minimal failing test (Red). Second, you write the simplest code possible to make the test pass (Green). Finally, you clean up the code and remove duplication while keeping the tests passing (Refactor).

Question 3

Why must I watch the test fail before writing code?

Accepted Answer

Watching a test fail confirms that the test is actually checking the intended behavior and isn't passing by accident. If a test passes immediately, it proves nothing about your new implementation.

Question 4

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

Accepted Answer

The Iron Law dictates that no production code can be written without a failing test appearing first. If code is accidentally written before a test, it must be deleted and restarted to ensure the test is truly validating the implementation.

Question 5

When is it acceptable to skip TDD using this skill?

Accepted Answer

Exceptions are only permitted for configuration files, documentation, pure styling tasks, or refactoring existing code that already has comprehensive test coverage.

Test-Driven Development (TDD)

주요 기능

사용 사례

Test-Driven Development (TDD)

주요 기능

사용 사례