TDD 工作流指南：红绿重构循环、三定律与实践原则 | 测试驱动开发

tdd-workflow by davila7/claude-code-templates

159 周安装量

23,500 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/davila7/claude-code-templates --skill tdd-workflow

方法论代码质量测试

🇨🇳中文介绍

TDD 工作流

先写测试，再写代码。

1. TDD 循环

🔴 红 → 编写失败的测试
    ↓
🟢 绿 → 编写最少的代码使其通过
    ↓
🔵 重构 → 改进代码质量
    ↓
   重复...

2. TDD 三定律

只有在为了让失败的测试通过时，才编写生产代码
只编写足够展示失败的测试
只编写足够让测试通过的代码

3. 红阶段原则

写什么

关注点	示例
行为	"应该将两个数字相加"
边界情况	"应该处理空输入"
错误状态	"应该为无效数据抛出异常"

红阶段规则

测试必须先失败
测试名称描述预期行为
每个测试一个断言（理想情况）

4. 绿阶段原则

最少代码

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

领域	操作
重复	提取公共代码
命名	使意图清晰
结构	改进组织
复杂度	简化逻辑

步骤	目的
准备	设置测试数据
执行	执行被测代码
断言	验证预期结果

场景	TDD 价值
新功能	高
错误修复	高（先写测试）
复杂逻辑	高
探索性	低（先探索，再用 TDD）
UI 布局	低

优先级	测试类型
1	正常路径
2	错误情况
3	边界情况
4	性能

❌ 不要	✅ 要做
跳过红阶段	先看测试失败
之后写测试	之前写测试
初始过度设计	保持简单
多个断言	每个测试一个行为
测试实现	测试行为

智能体	角色
智能体 A	编写失败的测试（红）
智能体 B	实现代码使其通过（绿）
智能体 C	优化（重构）

🇺🇸English

TDD Workflow

Write tests first, code second.

1. The TDD Cycle

🔴 RED → Write failing test
    ↓
🟢 GREEN → Write minimal code to pass
    ↓
🔵 REFACTOR → Improve code quality
    ↓
   Repeat...

2. The Three Laws of TDD

Write production code only to make a failing test pass
Write only enough test to demonstrate failure
Write only enough code to make the test pass

3. RED Phase Principles

What to Write

Focus	Example
Behavior	"should add two numbers"
Edge cases	"should handle empty input"
Error states	"should throw for invalid data"

RED Phase Rules

Test must fail first
Test name describes expected behavior
One assertion per test (ideally)

4. GREEN Phase Principles

Minimum Code

Principle	Meaning
YAGNI	You Aren't Gonna Need It
Simplest thing	Write the minimum to pass
No optimization	Just make it work

GREEN Phase Rules

Don't write unneeded code
Don't optimize yet
Pass the test, nothing more

5. REFACTOR Phase Principles

What to Improve

Area	Action
Duplication	Extract common code
Naming	Make intent clear
Structure	Improve organization
Complexity	Simplify logic

REFACTOR Rules

All tests must stay green
Small incremental changes
Commit after each refactor

6. AAA Pattern

Every test follows:

Step	Purpose
Arrange	Set up test data
Act	Execute code under test
Assert	Verify expected outcome

7. When to Use TDD

Scenario	TDD Value
New feature	High
Bug fix	High (write test first)
Complex logic	High
Exploratory	Low (spike, then TDD)
UI layout	Low

8. Test Prioritization

Priority	Test Type
1	Happy path
2	Error cases
3	Edge cases
4	Performance

9. Anti-Patterns

❌ Don't	✅ Do
Skip the RED phase	Watch test fail first
Write tests after	Write tests before
Over-engineer initial	Keep it simple
Multiple asserts	One behavior per test
Test implementation	Test behavior

10. AI-Augmented TDD

Multi-Agent Pattern

Agent	Role
Agent A	Write failing tests (RED)
Agent B	Implement to pass (GREEN)
Agent C	Optimize (REFACTOR)

Remember: The test is the specification. If you can't write a test, you don't understand the requirement.

Weekly Installs

139

Repository

davila7/claude-…emplates

GitHub Stars

22.6K

First Seen

Jan 25, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode115

claude-code112

gemini-cli110

codex103

cursor101

github-copilot99

YAGNI	你不需要它
最简单的事	编写最少的代码使其通过
不优化	先让它工作