Test with confidence, code with clarity

Your home for mastering Test-Driven Development through real-world katas and expert guidance.

Browse Katas Learn TDD Fundamentals
TDD Buddy Logo
Latest The Instruction File Is Not the Discipline

Kata Catalog

Practice TDD with a curated set of real-world katas, each with clear requirements and test cases.

Browse Katas

Guides & References

Learn best practices, naming conventions, and advanced TDD techniques from industry experts.

Explore Guides

Interactive Learning

Discover the TDD Gears model and learn how to apply TDD principles in real-world scenarios.

Learn More

Why TDD Matters More in the AI Era

The bar for "good tests" just moved. Agents made it non-optional.

  • The measurement should have ended the conversation. Adding a 'do TDD' instruction to the agent's prompt raised regressions by nearly two-thirds, from 6.08% to 9.94%. Contextual test discovery cut them by roughly seventy percent, down to 1.82%.
  • Discipline is a property of the test surface, not the directive. If the test for the function is one search away and reads like the domain, the agent runs it. If it is not, no amount of 'do TDD' in the prompt makes it visible.
  • The instruction file is the prose-spec drift trap, shrunk. A document positioned as the source of discipline, drifting from the running suite that actually shapes behavior. Same failure mode at a smaller scale.
  • The agent does TDD when the codebase already does. The instruction file is what teams reach for when the codebase does not, and the reach makes things measurably worse.

Read the argument: The Instruction File Is Not the Discipline

The Bar Moved

Old bar

Tests exist and pass. Good enough for humans with context.

New bar

Scenario names · builders · domain types · ubiquitous language. The test suite is the interface agents operate against.

Rich TDD isn't a style preference anymore. It's infrastructure for compressed-role, AI-augmented teams.

TDD Gears

Shift gears based on context, not habit

TDD Gears model showing Low, Medium, High, and Reverse gears for test-driven development

Low Gear

New territory. Build context. Small steps. Learn the shape of the problem before solving it.

Medium Gear

Patterns emerge. Apply design principles. Let the tests guide you toward better abstractions.

High Gear

Known patterns. Follow existing architecture. Move fast because the structure is already proven.

Reverse Gear

Wrong direction. Back up. Delete the test. Try a different approach. This isn't failure — it's steering.

Learn More About TDD Gears