Test-Driven Development (TDD) FAQs

Question 1

Can I skip TDD for simple prototypes?

Accepted Answer

While the skill is strict, it allows for exceptions such as throwaway prototypes or configuration files, provided you explicitly discuss and confirm these exceptions with your human partner.

Question 2

Does this TDD skill support refactoring?

Accepted Answer

Yes, refactoring is the third pillar of the cycle. Once the code is GREEN (passing), the skill encourages cleaning up duplication and improving names while ensuring all tests remain passing.

Question 3

Why does the skill insist on watching a test fail?

Accepted Answer

Watching a test fail (the RED phase) is the only way to prove that the test is actually testing the intended behavior and not passing due to a flaw in the test logic or existing code.

Question 4

How does this skill handle bug fixes?

Accepted Answer

For every bug fix, the skill requires writing a failing test that reproduces the reported issue before any implementation code is added, ensuring the fix is verified and preventing future regressions.

Question 5

What is the 'Iron Law' in this Claude Code skill?

Accepted Answer

The Iron Law states that no production code should be written without a failing test first. If code is written before the test, the skill mandates deleting it and starting over to ensure the test truly verifies the requirement.

Test-Driven Development (TDD)

Características Principales

Casos de Uso

Test-Driven Development (TDD)

Características Principales

Casos de Uso