tdd
Test-driven development with red-green-refactor loop. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests. Builds features one vertical slice at a time.
- License 许可
- MIT
- 最近更新
- 2026-07-07
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- tdd
- license
- MIT
- metadata
- { "source": "Adapted from mattpocock/skills (MIT)", "requires_codegraph": true }
- description
- Test-driven development with red-green-refactor loop. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests. Builds features one vertical slice at a time.
- compatibility
- opencode
03 SKILL.md 正文
Tool mapping (OpenCode): This skill uses:
questiontool for user promptstasktool for subagentsskill({ name: "..." })to load other skillscodegraph_explore,codegraph_searchfor codebase exploration (preferred)todowritefor phase/progress trackinggrep,glob,read,bashas fallbackContext rule: This skill supersedes any prior skill instructions. Follow ONLY these instructions now.
Test-Driven Development
Philosophy
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.
Anti-Pattern: Horizontal Slices
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:
- Tests written in bulk test imagined behavior, not actual behavior
- You end up testing the shape of things (data structures, function signatures) rather than user-facing behavior
- Tests become insensitive to real changes — they pass when behavior breaks, fail when behavior is fine
- You outrun your headlights, committing to test structure before understanding the implementation
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
...
Workflow
1. Planning
When exploring the codebase, read CONTEXT.md (if it exists) so that test names and interface vocabulary match the project's domain language, and respect ADRs in the area you're touching.
Before writing any code:
- [ ] Confirm with user what interface changes are needed
- [ ] Confirm with user which behaviors to test (prioritize)
- [ ] Identify opportunities for deep modules (small interface, deep implementation)
- [ ] List the behaviors to test (not implementation steps)
- [ ] Get user approval on the plan
Ask: "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.
2. Tracer Bullet
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.
3. Incremental Loop
For each remaining behavior:
RED: Write next test → fails
GREEN: Minimal code to pass → passes
Rules:
- One test at a time
- Only enough code to pass current test
- Don't anticipate future tests
- Keep tests focused on observable behavior
4. Refactor
After all tests pass, look for refactor candidates:
- [ ] Extract duplication
- [ ] Deepen modules (move complexity behind simple interfaces)
- [ ] Apply SOLID principles where natural
- [ ] Consider what new code reveals about existing code
- [ ] Run tests after each refactor step
Never refactor while RED. Get to GREEN first.
Checklist Per Cycle
[ ] 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
Integration with add-feature
When invoked as Phase 8 of add-feature, this skill replaces write-tests for the test-first path. Use the vertical-slice approach above instead of the bulk-generation approach.
NEVER
-
NEVER write all tests before any implementation Instead: One test → one implementation → repeat. Why: Horizontal slicing produces tests that test imagined behavior, not actual behavior.
-
NEVER test implementation details Instead: Assert the externally observable contract (return value, DB row, emitted event, HTTP response). Why: Tests that copy the implementation break on every refactor without catching real bugs.
-
NEVER mock the database or internal modules by default Instead: Use a real test DB; mock only at third-party API boundaries. Why: Mocked-DB tests diverge from production behavior — the failure mode this skill prevents.
-
NEVER refactor while RED Instead: Get to GREEN first, then refactor. Why: Refactoring with failing tests produces cascading failures that obscure the root cause.
-
NEVER skip the tracer bullet Instead: Write one trivial passing test before generating the rest. Why: A misconfigured runner produces false confidence — one green test proves the loop closes.
04 同仓库更多 Skills
write-tests
暂无简介
update-changelog
暂无简介
triage
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
to-prd
暂无简介
to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
testing-plan
暂无简介