Back to Details

bmad-test-strategy

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Quality Assurance Skill

质量保障Skill

When to Invoke

触发时机

Automatically activate when user:
  • Says "How should we test?", "Create test strategy"
  • Asks "Test plan?", "ATDD?", "Quality assurance?"
  • Mentions "testing", "test strategy", "QA"
  • Planning or architecture phase (for test strategy)
  • Uses words like: test, testing, strategy, QA, quality, ATDD
Specific trigger phrases:
  • "How should we test this?"
  • "Create test strategy"
  • "Test plan for [project]"
  • "ATDD scenarios"
  • "Quality assurance approach"
  • "Testing framework"
Can invoke:
  • During Phase 2 (Planning) for test strategy
  • During Phase 4 (Implementation) for ATDD
Do NOT invoke when:
  • No requirements yet (need PRD first)
  • Simple testing questions (answer directly)
  • Already have test strategy (reference existing)
当用户出现以下情况时自动激活：
  • 询问“我们应该如何测试？”、“创建测试策略”
  • 提问“测试计划？”、“ATDD？”、“质量保障？”
  • 提及“测试”、“测试策略”、“QA”
  • 处于规划或架构阶段（用于制定测试策略）
  • 使用以下词汇：test、testing、strategy、QA、quality、ATDD
特定触发短语：
  • “我们应该如何测试这个？”
  • “创建测试策略”
  • “[项目]的测试计划”
  • “ATDD场景”
  • “质量保障方案”
  • “测试框架”
可触发阶段：
  • 阶段2（规划阶段）：用于制定测试策略
  • 阶段4（实施阶段）：用于ATDD场景设计
请勿触发的情况：
  • 尚无需求（需先提供PRD）
  • 简单测试问题（直接作答即可）
  • 已存在测试策略（参考现有内容）

Mission

核心目标

Provide risk-focused quality strategies, acceptance tests, and governance that ensure BMAD deliverables meet agreed standards before release.
提供以风险为导向的质量策略、验收测试及管控机制，确保BMAD交付物在发布前符合约定标准。

Inputs Required

所需输入

  • prd_and_epics: requirements and roadmap produced by product-requirements skill
  • architecture: technical decisions and constraints
  • stories: delivery-planning outputs for upcoming work
  • existing_quality_assets: current test suites, tooling, and metrics
  • prd_and_epics：由产品需求Skill生成的需求与路线图
  • architecture：技术决策与约束条件
  • stories：待交付工作的交付规划输出
  • existing_quality_assets：当前的测试套件、工具及指标

Outputs

输出内容

  • Test strategy (from 
    assets/test-strategy-template.md.template
    )
  • ATDD scenarios (from 
    assets/atdd-scenarios-template.md.template
    )
  • Quality checklist (from 
    assets/quality-checklist-template.md.template
    )
  • Coverage matrices or CI/CD gate definitions stored with project docs
  • Recommendations for instrumentation, monitoring, or regression prevention
Template locations: 
.claude/skills/bmad-test-strategy/assets/*.template
  • 测试策略（基于
    assets/test-strategy-template.md.template
    模板）
  • ATDD场景（基于
    assets/atdd-scenarios-template.md.template
    模板）
  • 质量检查清单（基于
    assets/quality-checklist-template.md.template
    模板）
  • 存储在项目文档中的覆盖矩阵或CI/CD门禁定义
  • 关于监控埋点、运维监控或回归预防的建议
模板位置： 
.claude/skills/bmad-test-strategy/assets/*.template

Process

执行流程

  1. Confirm prerequisites using 
    CHECKLIST.md
    .
  2. Review requirements, architecture, and delivery plans to identify risk areas.
  3. Define quality approach (test types, automation, environments, data) proportionate to risk.
  4. Author executable artifacts (ATDD scenarios, scripts, dashboards) or instructions.
  5. Partner with development-execution and orchestrator to integrate quality gates and track follow-ups.
Note on automation: This skill currently operates through quality planning conversation using templates. No automation scripts are required—test strategies and ATDD scenarios are created manually using templates from 
assets/
. See 
scripts/README.md
for future automation roadmap.
  1. 使用
    CHECKLIST.md
    确认前置条件。
  2. 评审需求、架构及交付计划，识别风险区域。
  3. 定义与风险匹配的质量方案（测试类型、自动化、环境、数据）。
  4. 编写可执行工件（ATDD场景、脚本、仪表盘）或操作说明。
  5. 与开发执行团队及协调人员合作，集成质量门禁并跟踪后续工作。
自动化说明： 目前该Skill通过基于模板的质量规划对话开展工作。无需自动化脚本——测试策略和ATDD场景需使用
assets/
中的模板手动创建。未来自动化路线图请参考
scripts/README.md
。

Quality Gates

质量门禁

Ensure all checklist items are satisfied before sign-off. Traceability from requirements to test coverage must be explicit.
在签署确认前，需确保所有检查清单项均已满足。需求到测试覆盖的可追溯性必须明确。

Error Handling

错误处理

  • When prerequisites are missing, halt work and request specific artifacts.
  • If tools or environments are unavailable, document gaps and remediation plan.
  • Escalate high-risk issues (compliance, data privacy) immediately with evidence.
  • 当前置条件缺失时，暂停工作并请求特定工件。
  • 若工具或环境不可用，记录缺口及整改计划。
  • 立即上报高风险问题（合规性、数据隐私）并提供证据。