Test-Driven Development (TDD) FAQs

Question 1

Are there any exceptions to using TDD with this skill?

Accepted Answer

Exceptions are rare and typically include throwaway prototypes, generated code, or configuration files. For all other production code, TDD is the required standard.

Question 2

Can I use this skill for bug fixes?

Accepted Answer

Yes, it is highly recommended for bug fixes. You start by writing a test that reproduces the bug (Red), verify it fails, and then write the minimal code to fix it (Green).

Question 3

Does this skill support refactoring?

Accepted Answer

Absolutely. Refactoring is the third stage of the TDD cycle. This skill ensures you only refactor when all tests are green, allowing you to clean up code while maintaining functional integrity.

Question 4

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 before a test, the skill advises deleting it and starting over to ensure the test truly drives the implementation.

Question 5

What if my test passes immediately during the Red phase?

Accepted Answer

If a test passes immediately, it means you are testing existing behavior or the test is written incorrectly. The skill will prompt you to fix the test so it correctly identifies the missing feature or bug.

Test-Driven Development (TDD)

Key Features

Use Cases

Test-Driven Development (TDD)

Key Features

Use Cases