// Use when writing code test-first via red-green-refactor. Vertical-slice TDD: one failing test, then minimal code to pass. Triggers: TDD, test-first, red-green-refactor.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | tdd |
| description | Use when writing code test-first via red-green-refactor. Vertical-slice TDD: one failing test, then minimal code to pass. Triggers: TDD, test-first, red-green-refactor. |
| metadata | {"upstream":"mattpocock/skills/tdd","upstream-sha":"78f5077d6ec8c87a9cde9d485c098a149e5d5e2c","adapted-date":"2026-03-25"} |
Core principle: Tests should verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't.
Good tests are integration-style: they exercise real code paths through public APIs. They describe what the system does, not how it does it. A good test reads like a specification - "user can checkout with valid cart" tells you exactly what capability exists. These tests survive refactors because they don't care about internal structure.
Bad tests are coupled to implementation. They mock internal collaborators, test private methods, or verify through external means (like querying a database directly instead of using the interface). The warning sign: your test breaks when you refactor, but behavior hasn't changed. If you rename an internal function and tests fail, those tests were testing implementation, not behavior.
See ${CLAUDE_SKILL_DIR}/references/tests.md for examples and ${CLAUDE_SKILL_DIR}/references/mocking.md for mocking guidelines.
DO NOT write all tests first, then all implementation. This is "horizontal slicing" - treating RED as "write all tests" and GREEN as "write all code."
This produces crap tests:
Correct approach: Vertical slices via tracer bullets. One test -> one implementation -> repeat. Each test responds to what you learned from the previous cycle. Because you just wrote the code, you know exactly what behavior matters and how to verify it.
WRONG (horizontal):
RED: test1, test2, test3, test4, test5
GREEN: impl1, impl2, impl3, impl4, impl5
RIGHT (vertical):
RED->GREEN: test1->impl1
RED->GREEN: test2->impl2
RED->GREEN: test3->impl3
...
Before writing any code:
${CLAUDE_SKILL_DIR}/references/deep-modules.md${CLAUDE_SKILL_DIR}/references/interface-design.mdAsk: "What should the public interface look like? Which behaviors are most important to test?"
You can't test everything. Confirm with the user exactly which behaviors matter most. Focus testing effort on critical paths and complex logic, not every possible edge case.
Write ONE test that confirms ONE thing about the system:
RED: Write test for first behavior -> test fails
GREEN: Write minimal code to pass -> test passes
This is your tracer bullet - proves the path works end-to-end.
For each remaining behavior:
RED: Write next test -> fails
GREEN: Minimal code to pass -> passes
Rules:
After all tests pass, look for refactor candidates — see ${CLAUDE_SKILL_DIR}/references/refactoring.md:
Never refactor while RED. Get to GREEN first.
[ ] Test describes behavior, not implementation
[ ] Test uses public interface only
[ ] Test would survive internal refactor
[ ] Code is minimal for this test
[ ] No speculative features added