tdd
Guide Test-Driven Development using Kent Beck's Red-Green-Refactor cycle. Use when writing tests, implementing features via TDD, or following plan.md test instructions.
安装与使用
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
查看来源 ↗使用指南技能说明
INSTRUCTIONS
Follow Kent Beck's TDD and Tidy First principles using the three-phase workflow:
-
RED -
/tdd:red- Write ONE small failing test -
GREEN -
/tdd:green- Make it pass with minimal code, then commit -
REFACTOR -
/tdd:refactor- Improve structure without changing behavior, commit each step
Workflow Pattern
/tdd:red → write failing test → /tdd:green → pass test → /git:commit
↓
← next feature ← /tdd:red ← satisfied? ← /tdd:refactor (repeat as needed)
Core Principles
- One test at a time: Each RED adds exactly ONE failing test
- Minimal code: GREEN phase writes just enough to pass
- Never skip REFACTOR: Every TDD cycle must complete all three phases
- Tidy First: Separate structural changes (refactor) from behavioral changes (feat/fix)
- Small commits: Commit after GREEN, commit after EACH refactor step
Strategy Selection (GREEN Phase)
| Confidence | Strategy | Use When |
|---|---|---|
| Low | Fake It | Return constant, generalize later |
| High | Obvious Implementation | Solution is clear |
| Generalizing | Triangulation | Add test to break a fake |
Quality Standards
- Eliminate duplication between test and production code
- Express intent through clear naming
- Keep methods small and focused
- Run ALL tests after EVERY change
使用示例
查看来源仓库中的使用示例与配置说明。
查看来源 ↗来源历史
- 收录时间
- 2026-01-20
- 索引更新时间
- 2026-01-26
- Branch
- main
收录与同步日期属于本站记录。源码修改历史请查看来源仓库。
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!