Test-Driven Development (TDD) FAQs

Question 1

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

Accepted Answer

The Iron Law dictates that no production code can be written without a failing test first. If code is written prematurely, it must be deleted and restarted following the TDD cycle.

Question 2

How does this skill integrate with SuperSpec?

Accepted Answer

It identifies scenarios defined in your SuperSpec markdown files and treats each one as a mandatory TDD test case that must pass before the feature is considered complete.

Question 3

Why is the RED phase mandatory?

Accepted Answer

Watching a test fail (the RED phase) is the only way to prove the test is actually testing the new functionality and isn't passing by accident or due to existing logic.

Question 4

What kind of TDD evidence is required?

Accepted Answer

Users must provide snapshots of the failing test code, the terminal output showing the failure, the implementation code, and finally the terminal output showing the passing test.

Question 5

Does this skill support refactoring?

Accepted Answer

Yes, the 'Refactor' phase is a core part of the cycle. Once the code is 'Green' (passing), the skill encourages cleaning up the logic while ensuring the tests stay passing.

Test-Driven Development (TDD)

Key Features

Use Cases

Test-Driven Development (TDD)

Key Features

Use Cases