Test-Driven Development (TDD) FAQs

Question 1

Does this work with all testing frameworks?

Accepted Answer

Yes, the skill is framework-agnostic and provides specific patterns for popular runners like npm, pytest, cargo, and others.

Question 2

How does this improve code quality?

Accepted Answer

By writing tests first, you focus on the API and behavior rather than implementation details. This results in cleaner code, fewer regressions, and better documented requirements.

Question 3

Why does the skill require test output evidence?

Accepted Answer

Requiring evidence (pasting terminal output) ensures that the test actually fails for the correct reason, preventing 'false positives' where a test passes or fails for the wrong implementation details.

Question 4

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

Accepted Answer

The Iron Law states that no production code may be written without first creating a failing test that verifies the intended behavior. If code is written first, the skill mandates deleting it and starting over.

Question 5

Can I use this for existing codebases?

Accepted Answer

Absolutely. It is highly effective for bug fixes and refactoring in existing projects by first defining the desired behavior through a test before modifying any logic.

Test-Driven Development (TDD)

주요 기능

사용 사례

Test-Driven Development (TDD)

주요 기능

사용 사례