Test-Driven Development (TDD) FAQs

Question 1

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

Accepted Answer

The Iron Law dictates that no production code is written without a failing test first. If production code is accidentally written before a test, it must be deleted to ensure a clean test-first implementation.

Question 2

How does this skill handle the Red-Green-Refactor cycle?

Accepted Answer

It guides users to write a failing test (Red), implement the minimum code needed to pass (Green), and then clean up the code (Refactor) while ensuring the tests remain passing throughout.

Question 3

When can TDD be skipped while using this skill?

Accepted Answer

Exceptions are rare and include throwaway prototypes, generated code, or configuration files, but these should only be skipped after explicit confirmation from the human partner.

Question 4

Why is it mandatory to watch a test fail first?

Accepted Answer

Watching a test fail proves the test is valid and specifically targets the missing feature or bug. Tests that pass immediately provide no proof they are actually testing the intended behavior.

Question 5

Can I use this skill for bug fixes?

Accepted Answer

Yes, it is highly recommended for bug fixes. You must first write a test that reproduces the bug, watch it fail, and then implement the fix to make the test turn green.

Test-Driven Development (TDD)

About

Key Features

Use Cases

Test-Driven Development (TDD)

About

Key Features

Use Cases