Test-Driven Development (TDD) FAQs

Question 1

Are there any exceptions to using this TDD skill?

Accepted Answer

Exceptions are rare but include throwaway prototypes, generated code, or simple configuration files, though it is recommended to consult with a human partner before skipping the workflow.

Question 2

Why shouldn't I just write tests after the code is finished?

Accepted Answer

Tests written after implementation often suffer from bias and may pass immediately without proving they can actually catch errors. TDD ensures the test is valid by watching it fail first.

Question 3

How does the Red-Green-Refactor cycle work in Claude Code?

Accepted Answer

You first write a minimal failing test (RED), verify the failure, write the simplest possible code to pass (GREEN), verify the pass, and finally clean up the code (REFACTOR) while keeping the tests green.

Question 4

Can I use this skill for bug fixing?

Accepted Answer

Yes. This skill requires you to write a failing test that reproduces the reported bug before any fixes are applied, ensuring the fix is verified and prevents future regressions.

Question 5

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 and restarted from the test phase.

Test-Driven Development (TDD)

主な機能

ユースケース

Test-Driven Development (TDD)

主な機能

ユースケース