Test-Driven Development (TDD) FAQs

Question 1

How does the skill handle the 'tactical programming' trap?

Accepted Answer

It includes John Ousterhout's counterpoint to TDD, encouraging the developer to step back from feature-specific tests to evaluate the overall architectural design periodically.

Question 2

What testing patterns does it support?

Accepted Answer

The skill supports various patterns including Triangulation (using multiple examples to drive generalization), Starting with the Assertion, and Obvious Implementation.

Question 3

What is the core workflow of the TDD skill?

Accepted Answer

It follows the classic Red-Green-Refactor cycle: first writing a failing test to define behavior, then implementing the minimal code necessary to pass, and finally refactoring for clean design.

Question 4

Can I use this for UI and styling changes?

Accepted Answer

TDD is best suited for logic and API design. For pure UI/styling changes or exploratory prototypes, the skill recommends skipping the strict TDD flow to maintain velocity.

Question 5

Does this skill work with existing legacy code?

Accepted Answer

Yes, it incorporates Michael Feathers' techniques for working with legacy code, focusing on creating characterization tests to provide a safety net for modernizing older systems.

Test-Driven Development (TDD)

Key Features

Use Cases

Test-Driven Development (TDD)

Key Features

Use Cases