Test-Driven Development (TDD) Mastery FAQs

Question 1

What is the benefit of writing minimal code during the Green phase?

Accepted Answer

Writing the simplest code to pass a test prevents over-engineering and keeps the implementation focused strictly on the requirements defined by your tests.

Question 2

When should I skip TDD according to this skill?

Accepted Answer

TDD should always be used for features and bug fixes. Exceptions are only made for throwaway prototypes, generated code, or configuration files after consulting with a human partner.

Question 3

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

Accepted Answer

The Iron Law states that no production code should be written without a failing test first. If code is written before a test, it must be deleted and started over to ensure the test truly verifies the intended behavior.

Question 4

Does this skill work for bug fixes?

Accepted Answer

Yes. The skill requires writing a failing test that reproduces the bug before any fix is implemented, proving the fix works and preventing future regressions.

Question 5

Why must I watch the test fail (Verify Red phase)?

Accepted Answer

Watching a test fail confirms that the test is actually checking for the missing feature or bug. If a test passes immediately, it isn't testing anything new or the test logic is incorrect.

Test-Driven Development (TDD) Mastery

主要功能

使用场景

Test-Driven Development (TDD) Mastery

主要功能

使用场景