affaan-m/ECC/docs/zh-CN/skills/tdd-workflow/SKILL.md
tdd-workflow
Use it for testing and engineering tasks; the detail page covers purpose, installation, and practical steps.
- Source repository stars
- 234,327
- Declared platforms
- 0
- Static risk flags
- 2
- Last source update
- 2026-07-27
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
此技能确保所有代码开发遵循TDD原则,并具备全面的测试覆盖率。
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/affaan-m/ECC --skill "docs/zh-CN/skills/tdd-workflow"Inspect the Agent Skill "tdd-workflow" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/docs/zh-CN/skills/tdd-workflow/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
何时激活
编写新功能或功能 修复错误或问题 重构现有代码 添加API端点 创建新组件
编写新功能或功能修复错误或问题重构现有代码 - 02
核心原则
最低80%覆盖率(单元 + 集成 + 端到端) 覆盖所有边缘情况 测试错误场景 验证边界条件
最低80%覆盖率(单元 + 集成 + 端到端)覆盖所有边缘情况测试错误场景 - 03
1. 测试优先于代码
Review the “1. 测试优先于代码” section in the pinned source before continuing.
Review and apply the “1. 测试优先于代码” source section. - 04
2. 覆盖率要求
最低80%覆盖率(单元 + 集成 + 端到端) 覆盖所有边缘情况 测试错误场景 验证边界条件
最低80%覆盖率(单元 + 集成 + 端到端)覆盖所有边缘情况测试错误场景 - 05
3. 测试类型
单个函数和工具 组件逻辑 纯函数 辅助函数和工具
单个函数和工具组件逻辑纯函数
Permission review
Static risk signals and limitations
Runs scripts
The documentation asks the agent to run terminal commands or scripts.
npm testRuns scripts
The documentation asks the agent to run terminal commands or scripts.
npm testNetwork access
The documentation includes network, browsing, or remote request actions.
const request = new NextRequest('http://localhost/api/markets')Network access
The documentation includes network, browsing, or remote request actions.
const request = new NextRequest('http://localhost/api/markets?limit=invalid')Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 65/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 234,327 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- affaan-m/ECC
- Skill path
- docs/zh-CN/skills/tdd-workflow/SKILL.md
- Commit
- 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
测试驱动开发工作流
此技能确保所有代码开发遵循TDD原则,并具备全面的测试覆盖率。
何时激活
- 编写新功能或功能
- 修复错误或问题
- 重构现有代码
- 添加API端点
- 创建新组件
核心原则
1. 测试优先于代码
始终先编写测试,然后实现代码以使测试通过。
2. 覆盖率要求
- 最低80%覆盖率(单元 + 集成 + 端到端)
- 覆盖所有边缘情况
- 测试错误场景
- 验证边界条件
3. 测试类型
单元测试
- 单个函数和工具
- 组件逻辑
- 纯函数
- 辅助函数和工具
集成测试
- API端点
- 数据库操作
- 服务交互
- 外部API调用
端到端测试 (Playwright)
- 关键用户流程
- 完整工作流
- 浏览器自动化
- UI交互
TDD 工作流步骤
步骤 1: 编写用户旅程
作为一个[角色],我希望能够[行动],以便[获得收益]
示例:
作为一个用户,我希望能够进行语义搜索市场,
这样即使没有精确的关键词,我也能找到相关的市场。
步骤 2: 生成测试用例
针对每个用户旅程,创建全面的测试用例:
describe('Semantic Search', () => {
it('returns relevant markets for query', async () => {
// Test implementation
})
it('handles empty query gracefully', async () => {
// Test edge case
})
it('falls back to substring search when Redis unavailable', async () => {
// Test fallback behavior
})
it('sorts results by similarity score', async () => {
// Test sorting logic
})
})
步骤 3: 运行测试(它们应该失败)
npm test
# Tests should fail - we haven't implemented yet
步骤 4: 实现代码
编写最少的代码以使测试通过:
// Implementation guided by tests
export async function searchMarkets(query: string) {
// Implementation here
}
步骤 5: 再次运行测试
npm test
# Tests should now pass
步骤 6: 重构
在保持测试通过的同时提高代码质量:
- 消除重复
- 改进命名
- 优化性能
- 增强可读性
步骤 7: 验证覆盖率
npm run test:coverage
# Verify 80%+ coverage achieved
测试模式
单元测试模式 (Jest/Vitest)
import { render, screen, fireEvent } from '@testing-library/react'
import { Button } from './Button'
describe('Button Component', () => {
it('renders with correct text', () => {
render(<Button>Click me</Button>)
expect(screen.getByText('Click me')).toBeInTheDocument()
})
it('calls onClick when clicked', () => {
const handleClick = jest.fn()
render(<Button onClick={handleClick}>Click</Button>)
fireEvent.click(screen.getByRole('button'))
expect(handleClick).toHaveBeenCalledTimes(1)
})
it('is disabled when disabled prop is true', () => {
render(<Button disabled>Click</Button>)
expect(screen.getByRole('button')).toBeDisabled()
})
})
API 集成测试模式
import { NextRequest } from 'next/server'
import { GET } from './route'
describe('GET /api/markets', () => {
it('returns markets successfully', async () => {
const request = new NextRequest('http://localhost/api/markets')
const response = await GET(request)
const data = await response.json()
expect(response.status).toBe(200)
expect(data.success).toBe(true)
expect(Array.isArray(data.data)).toBe(true)
})
it('validates query parameters', async () => {
const request = new NextRequest('http://localhost/api/markets?limit=invalid')
const response = await GET(request)
expect(response.status).toBe(400)
})
it('handles database errors gracefully', async () => {
// Mock database failure
const request = new NextRequest('http://localhost/api/markets')
// Test error handling
})
})
端到端测试模式 (Playwright)
import { test, expect } from '@playwright/test'
test('user can search and filter markets', async ({ page }) => {
// Navigate to markets page
await page.goto('/')
await page.click('a[href="/markets"]')
// Verify page loaded
await expect(page.locator('h1')).toContainText('Markets')
// Search for markets
await page.fill('input[placeholder="Search markets"]', 'election')
// Wait for debounce and results
await page.waitForTimeout(600)
// Verify search results displayed
const results = page.locator('[data-testid="market-card"]')
await expect(results).toHaveCount(5, { timeout: 5000 })
// Verify results contain search term
const firstResult = results.first()
await expect(firstResult).toContainText('election', { ignoreCase: true })
// Filter by status
await page.click('button:has-text("Active")')
// Verify filtered results
await expect(results).toHaveCount(3)
})
test('user can create a new market', async ({ page }) => {
// Login first
await page.goto('/creator-dashboard')
// Fill market creation form
await page.fill('input[name="name"]', 'Test Market')
await page.fill('textarea[name="description"]', 'Test description')
await page.fill('input[name="endDate"]', '2025-12-31')
// Submit form
await page.click('button[type="submit"]')
// Verify success message
await expect(page.locator('text=Market created successfully')).toBeVisible()
// Verify redirect to market page
await expect(page).toHaveURL(/\/markets\/test-market/)
})
测试文件组织
src/
├── components/
│ ├── Button/
│ │ ├── Button.tsx
│ │ ├── Button.test.tsx # 单元测试
│ │ └── Button.stories.tsx # Storybook
│ └── MarketCard/
│ ├── MarketCard.tsx
│ └── MarketCard.test.tsx
├── app/
│ └── api/
│ └── markets/
│ ├── route.ts
│ └── route.test.ts # 集成测试
└── e2e/
├── markets.spec.ts # 端到端测试
├── trading.spec.ts
└── auth.spec.ts
模拟外部服务
Supabase 模拟
jest.mock('@/lib/supabase', () => ({
supabase: {
from: jest.fn(() => ({
select: jest.fn(() => ({
eq: jest.fn(() => Promise.resolve({
data: [{ id: 1, name: 'Test Market' }],
error: null
}))
}))
}))
}
}))
Redis 模拟
jest.mock('@/lib/redis', () => ({
searchMarketsByVector: jest.fn(() => Promise.resolve([
{ slug: 'test-market', similarity_score: 0.95 }
])),
checkRedisHealth: jest.fn(() => Promise.resolve({ connected: true }))
}))
OpenAI 模拟
jest.mock('@/lib/openai', () => ({
generateEmbedding: jest.fn(() => Promise.resolve(
new Array(1536).fill(0.1) // Mock 1536-dim embedding
))
}))
测试覆盖率验证
运行覆盖率报告
npm run test:coverage
覆盖率阈值
{
"jest": {
"coverageThresholds": {
"global": {
"branches": 80,
"functions": 80,
"lines": 80,
"statements": 80
}
}
}
}
应避免的常见测试错误
FAIL: 错误:测试实现细节
// Don't test internal state
expect(component.state.count).toBe(5)
PASS: 正确:测试用户可见的行为
// Test what users see
expect(screen.getByText('Count: 5')).toBeInTheDocument()
FAIL: 错误:脆弱的定位器
// Breaks easily
await page.click('.css-class-xyz')
PASS: 正确:语义化定位器
// Resilient to changes
await page.click('button:has-text("Submit")')
await page.click('[data-testid="submit-button"]')
FAIL: 错误:没有测试隔离
// Tests depend on each other
test('creates user', () => { /* ... */ })
test('updates same user', () => { /* depends on previous test */ })
PASS: 正确:独立的测试
// Each test sets up its own data
test('creates user', () => {
const user = createTestUser()
// Test logic
})
test('updates user', () => {
const user = createTestUser()
// Update logic
})
持续测试
开发期间的监视模式
npm test -- --watch
# Tests run automatically on file changes
预提交钩子
# Runs before every commit
npm test && npm run lint
CI/CD 集成
# GitHub Actions
- name: Run Tests
run: npm test -- --coverage
- name: Upload Coverage
uses: codecov/codecov-action@v3
最佳实践
- 先写测试 - 始终遵循TDD
- 每个测试一个断言 - 专注于单一行为
- 描述性的测试名称 - 解释测试内容
- 组织-执行-断言 - 清晰的测试结构
- 模拟外部依赖 - 隔离单元测试
- 测试边缘情况 - Null、undefined、空、大量数据
- 测试错误路径 - 不仅仅是正常路径
- 保持测试快速 - 单元测试每个 < 50ms
- 测试后清理 - 无副作用
- 审查覆盖率报告 - 识别空白
成功指标
- 达到 80%+ 代码覆盖率
- 所有测试通过(绿色)
- 没有跳过或禁用的测试
- 快速测试执行(单元测试 < 30秒)
- 端到端测试覆盖关键用户流程
- 测试在生产前捕获错误
记住:测试不是可选的。它们是安全网,能够实现自信的重构、快速的开发和生产的可靠性。
Alternatives
Compare before choosing
affaan-m/ECC
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
affaan-m/ECC
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
affaan-m/ECC
tdd-workflow
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
affaan-m/ECC
tdd-workflow
Use it for testing and engineering tasks; the detail page covers purpose, installation, and practical steps.