Test-Driven Development (TDD) FAQs

Question 1

Does this skill allow for writing tests after implementation?

Accepted Answer

No, this skill strictly enforces writing the test before the implementation. This ensures the test actually verifies the intended behavior by proving it fails when the feature is missing.

Question 2

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

Accepted Answer

The Iron Law mandates that no production code can be written without a failing test existing first. If code is written before a test, the skill requires immediate deletion of that code to maintain TDD integrity.

Question 3

Which testing frameworks are supported?

Accepted Answer

The skill natively checks for and supports popular frameworks including Jest and Vitest for JavaScript/TypeScript, Pytest for Python, and PHPUnit or Pest for PHP.

Question 4

What happens if a test passes immediately during the RED phase?

Accepted Answer

If a test passes immediately, it indicates you are testing existing behavior or the test is invalid. The skill requires you to fix the test so that it fails before proceeding to the GREEN phase.

Question 5

When should I use this skill?

Accepted Answer

You should use this skill whenever you are starting a new feature, implementing a bug fix, or performing a refactor where behavior changes must be verified.

Test-Driven Development (TDD)

주요 기능

사용 사례

Test-Driven Development (TDD)

주요 기능

사용 사례