Strict Test-Driven Development (TDD) FAQs

Question 1

Is TDD slower than normal coding?

Accepted Answer

While it may feel slower initially, TDD is faster in the long run because it significantly reduces time spent on debugging, manual verification, and fixing regressions.

Question 2

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

Accepted Answer

If a test passes immediately, it means you are testing existing behavior or the test is invalid. The skill will prompt you to fix the test until it fails for the right reason.

Question 3

Why does this skill insist on deleting code written before tests?

Accepted Answer

This prevents 'tests-after' bias. Writing tests for existing code often results in tests that pass by default without ever proving they can catch a failure, which defeats the core purpose of TDD.

Question 4

Can I use this skill for bug fixes?

Accepted Answer

Absolutely. The skill requires you to write a failing test that reproduces the bug first, ensuring the fix actually works and preventing that specific bug from ever returning.

Question 5

Does this skill support specific testing frameworks?

Accepted Answer

The TDD methodology is language-agnostic. It works with any test runner (like Jest, Pytest, or Vitest) that your project is configured to use.

Strict Test-Driven Development (TDD)

주요 기능

사용 사례

Strict Test-Driven Development (TDD)

주요 기능

사용 사례