Test-Driven Development (TDD) FAQs

Question 1

What is the core rule of the TDD skill?

Accepted Answer

The fundamental rule is 'No code without a failing test first.' You must watch a test fail for the expected reason before writing any implementation code.

Question 2

What happens if a test passes immediately?

Accepted Answer

If a test passes immediately, it proves nothing about your new code. You must fix the test so it fails first to ensure it is capable of catching the bug or verifying the new feature.

Question 3

Should I use TDD for every task?

Accepted Answer

No. TDD is recommended for complex logic, algorithms, and business rules. You should skip it for UI components, simple CRUD operations, and straightforward mappings.

Question 4

Does this skill work with React or UI components?

Accepted Answer

This skill specifically advises skipping TDD for UI components, recommending manual testing, typechecking, and linting as more appropriate verification methods for front-end work.

Question 5

Why does the skill require deleting code written before a test?

Accepted Answer

To ensure the test is actually driving the implementation. Keeping pre-written code often leads to 'testing the implementation' rather than 'testing the behavior,' which lowers confidence.

Test-Driven Development (TDD)

Key Features

Use Cases

Test-Driven Development (TDD)

Key Features

Use Cases