Test-Driven Development (TDD) Mastery FAQs

Question 1

How does this skill handle the Red-Green-Refactor cycle?

Accepted Answer

It enforces a cycle where you write a failing test (Red), verify the failure message, write the minimal code required to pass (Green), verify the pass across the suite, and then clean up the code (Refactor) while remaining in a green state.

Question 2

When should I use this TDD skill?

Accepted Answer

This skill should be applied to all new features, bug fixes, behavior changes, and refactoring tasks. Exceptions are generally limited to throwaway prototypes or generated configuration files.

Question 3

Can I use mocks with this skill?

Accepted Answer

The skill encourages testing real behavior and real code. It advises that mocks should only be used when absolutely unavoidable to avoid the common pitfall of testing mock behavior instead of implementation.

Question 4

Why does the skill insist on deleting code written before tests?

Accepted Answer

Writing tests after code often results in tests that pass immediately without proving they can catch a failure. Deleting and restarting with TDD ensures the test is biased toward requirements rather than the existing implementation.

Question 5

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

Accepted Answer

The Iron Law mandates that no production code should be written without first creating a failing test. If code is written beforehand, it must be deleted and restarted from the test to ensure the test actually verifies the behavior.

Test-Driven Development (TDD) Mastery

Test-Driven Development (TDD) Mastery

소개

주요 기능

사용 사례

소개

주요 기능

사용 사례