Test-Driven Development (TDD) Mastery FAQs

Question 1

Can I use this skill for existing legacy code?

Accepted Answer

Absolutely. When modifying existing code, the skill guides you to add tests for the current behavior or the new desired behavior before making any implementation changes.

Question 2

Why does the skill insist on watching a test fail?

Accepted Answer

Watching a test fail (Verify RED) proves that the test is actually checking the intended behavior and isn't passing accidentally due to a configuration error or existing code.

Question 3

Does this skill work for bug fixes?

Accepted Answer

Yes. The skill requires you to write a failing test that reproduces the bug before any fix is implemented, ensuring the bug is truly understood and solved.

Question 4

What is the 'Iron Law' enforced by this skill?

Accepted Answer

The Iron Law dictates that no production code should be written without a failing test first. If code is written before the test, this skill advocates for deleting it and starting over to ensure the test is valid.

Question 5

What is the Red-Green-Refactor cycle?

Accepted Answer

It is a three-step process: RED (write a failing test), GREEN (write the minimal code to make the test pass), and REFACTOR (clean up the code while keeping the tests passing).

Test-Driven Development (TDD) Mastery

주요 기능

사용 사례

Test-Driven Development (TDD) Mastery

주요 기능

사용 사례