Test-Driven Development (TDD) FAQs

Question 1

How does the Red-Green-Refactor cycle work here?

Accepted Answer

First, you write a failing test (Red). Second, you must verify the failure in the console. Third, you write the minimal code to pass (Green). Finally, you refactor the code while keeping the tests green.

Question 2

Why is watching the test fail (the Red phase) mandatory?

Accepted Answer

If you don't see the test fail, you cannot be sure the test is actually testing the right thing or that it wouldn't pass anyway due to a configuration error, leading to a false sense of security.

Question 3

What is the core rule of the TDD skill?

Accepted Answer

The 'Iron Law' is that no production code can be written without a failing test first. If production code is written before the test, the skill dictates it must be deleted and restarted to ensure the test truly validates the implementation.

Question 4

Can this skill help with bug fixing?

Accepted Answer

Yes. It mandates a workflow where you first write a failing test that reproduces the bug, verify the failure, and then implement the fix, ensuring the bug never regresses.

Question 5

Which programming languages and frameworks are supported?

Accepted Answer

The skill is language-agnostic and works with any framework that has a CLI-based test runner, such as Jest (Node.js), Pytest (Python), or xUnit/nUnit (.NET).

Test-Driven Development (TDD)

主要功能

使用场景

Test-Driven Development (TDD)

主要功能

使用场景