Test-Driven Development (TDD) FAQs

Question 1

Why does this skill suggest deleting code written before a test?

Accepted Answer

Writing tests after code often results in tests that pass immediately without proving they actually catch errors. Deleting and restarting ensures the test truly verifies the intended behavior.

Question 2

Does this skill help with code refactoring?

Accepted Answer

Absolutely. The 'Refactor' phase is the third step of the core cycle, allowing for code cleanup and optimization only after you have reached a 'Green' passing state.

Question 3

How does TDD improve development speed in the long run?

Accepted Answer

While it requires more upfront effort, TDD reduces time spent on debugging, prevents regressions, and acts as living documentation, making the codebase easier to maintain.

Question 4

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

Accepted Answer

The Iron Law states that no production code should be written without first having a failing test that demonstrates the need for that code. If code is written before a test, it should be deleted.

Question 5

Can I use this skill for bug fixes?

Accepted Answer

Yes, it is highly recommended. The skill guides you to write a failing test that reproduces the bug, ensuring the fix is verified and preventing future regressions.

Test-Driven Development (TDD)

소개

주요 기능

사용 사례

Test-Driven Development (TDD)

소개

주요 기능

사용 사례