Test with confidence, code with clarity

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

TDD Buddy Logo
Latest The Agent's Memory Is Not a Test Suite

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.

  • Persistent memory is being sold as the next harness layer. A 2026 wave of papers and tools (arxiv 2606.30306 survey, arxiv 2609.05510 operational report, arxiv 2606.12329 PROJECTMEM, arxiv 2604.27283 abstention-aware retrieval, the NeurIPS 2026 selective-retrieval paper) proposes cross-session memory as the fix for coding agents that forget what they already learned. The pitch is real and the layer is real.
  • Memory without validation propagates past wrong fixes. Naive similarity retrieval shipped a 75% false-positive rate on one hard-negative benchmark. Agents re-apply the fix that passed last time to the case it does not actually fit. The memory is faithfully doing its job and the suite is still the authority that catches the propagation.
  • Selective retrieval helps because it is a test-discipline move. The NeurIPS result (29 of 94 resolved with validated-episode retrieval versus 19 of 94 with none) is what works. The mechanism is a validation gate the memory writes through, not the memory itself. Memory earns its keep when the suite told it the past fix was correct for this family of cases.
  • When memory and the suite disagree, the suite wins. A memory system is a cache of past readings that can be stale, wrong, or irrelevant to this change. The test the agent reads before every write is the primary signal; the memory is a hint. Any workflow that treats the memory as authoritative is selling the agent its own homework as the verifier.

Read the argument: The Agent's Memory Is Not a Test Suite

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.

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.