Test-Driven Development (TDD) FAQs

Question 1

When is it acceptable to skip TDD with this skill?

Accepted Answer

TDD is mandatory except for throwaway prototypes, generated code, or configuration files, and even then, skipping should be discussed with the human partner.

Question 2

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

Accepted Answer

The Iron Law dictates that no production code should be written without a failing test first; if code is written beforehand, it must be deleted and restarted to ensure the test is valid.

Question 3

Why does this skill mandate 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 by accident or due to a flaw in the testing logic.

Question 4

How does this skill handle refactoring?

Accepted Answer

After reaching a 'Green' state (passing test), the skill guides you to clean up the code and remove duplication while continuously verifying that the tests remain green.

Question 5

Can I use this skill for fixing existing bugs?

Accepted Answer

Yes, it requires writing a failing test that reproduces the specific bug before any fix is implemented, ensuring the fix works and preventing future regressions.

Test-Driven Development (TDD)

Key Features

Use Cases

Test-Driven Development (TDD)

Key Features

Use Cases