TDD Protocol FAQs

Question 1

Can I use this skill for existing projects without tests?

Accepted Answer

Yes. When adding features or fixing bugs in existing code, the skill guides you to add tests for that specific area first, gradually improving the test coverage of the project.

Question 2

What is the TDD Iron Law in this 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, the protocol requires deleting it and starting over to ensure the test truly verifies the behavior.

Question 3

How does the Red-Green-Refactor cycle work?

Accepted Answer

It follows a three-step process: RED (write a failing test), GREEN (write minimal code to pass the test), and REFACTOR (clean up the code while ensuring tests stay passing).

Question 4

Why is it mandatory to watch a test fail first?

Accepted Answer

Watching a test fail confirms that the test is actually checking the intended behavior and isn't passing by accident or testing the wrong thing.

Question 5

What should I do if a test is too hard to write?

Accepted Answer

TDD often reveals design flaws. If a test is too complicated, it usually means the code design is too coupled or complex, signaling that you should simplify the interface.

TDD Protocol

About

Key Features

Use Cases

TDD Protocol

About

Key Features

Use Cases