holistic-testing-pact
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseHolistic Testing Model with PACT Principles
融合PACT原则的整体测试模型
<default_to_action>
When designing test strategies or building quality into teams:
- APPLY PACT principles: Proactive (test before bugs), Autonomous (teams own quality), Collaborative (whole-team responsibility), Targeted (risk-focused)
- IDENTIFY quadrant focus: Technology-facing (unit, integration, performance) or Business-facing (acceptance, exploratory, usability)
- SELECT agents based on PACT dimension and testing quadrant
- IMPLEMENT feedback loops that catch issues in minutes, not days
- MEASURE outcomes (bug escape rate, release confidence) not activities (test count)
Quick PACT Application:
- Proactive → Design testability into architecture, risk analysis during refinement
- Autonomous → Devs run tests locally, CI pipeline with no manual gates
- Collaborative → Three Amigos, QE pairs with dev, shared test ownership
- Targeted → Risk-based planning, focus on critical flows, kill valueless tests
Critical Success Factors:
- Quality is a whole-team responsibility, not a QA phase
- QA as enablers (build infrastructure, coach), not gatekeepers
- Fast feedback during development, not after </default_to_action>
<default_to_action>
在设计测试策略或为团队构建质量文化时：
- 应用PACT原则：前瞻性（在bug出现前测试）、自主性（团队对质量负责）、协作性（全员承担质量责任）、针对性（聚焦风险）
- 明确象限重点：面向技术（单元测试、集成测试、性能测试）或面向业务（验收测试、探索性测试、可用性测试）
- 根据PACT维度和测试象限选择Agent
- 实施能在数分钟内发现问题的反馈闭环，而非数天
- 衡量结果（bug逃逸率、发布信心）而非活动（测试用例数量）
PACT快速应用指南：
- 前瞻性 → 在架构设计中融入可测试性，在需求细化阶段开展风险分析
- 自主性 → 开发者本地运行测试，CI流水线无需人工审批
- 协作性 → 三方协作（业务、开发、测试），测试人员与开发结对，共享测试所有权
- 针对性 → 基于风险规划，聚焦关键流程，剔除无价值测试
关键成功因素：
- 质量是全员责任，而非仅QA阶段的工作
- QA的角色是赋能者（搭建基础设施、提供指导），而非守门员
- 在开发过程中快速反馈，而非事后反馈 </default_to_action>
Quick Reference Card
速查卡片
When to Use
适用场景
- Designing comprehensive test strategies
- Building quality culture in teams
- Choosing testing approach for new projects
- Evolving from sequential QA to concurrent quality
- 设计全面的测试策略
- 在团队中构建质量文化
- 为新项目选择测试方法
- 从串行QA模式转型为并行质量保障模式
PACT Principles
PACT原则
| Principle | Focus | Anti-Pattern |
|---|---|---|
| Proactive | Test before code, design testability | Waiting for bugs to find you |
| Autonomous | Teams deploy when ready | QA as manual gatekeepers |
| Collaborative | Whole-team quality thinking | QA works in isolation |
| Targeted | Risk-based, high-value tests | Exhaustive checkbox testing |
| 原则 | 核心聚焦 | 反模式 |
|---|---|---|
| 前瞻性 | 编码前测试，设计可测试性架构 | 被动等待bug出现 |
| 自主性 | 团队自主决定部署时机 | QA作为人工守门员 |
| 协作性 | 全员具备质量思维 | QA孤立工作 |
| 针对性 | 基于风险的高价值测试 | 无差别全覆盖式测试 |
Holistic Testing Quadrants
整体测试象限
| Quadrant | Purpose | Examples |
|---|---|---|
| Tech + Support | Fast feedback | Unit, component, integration tests |
| Tech + Critique | Find limits | Performance, security, chaos |
| Business + Support | Shared understanding | BDD, acceptance tests |
| Business + Critique | Discover unknowns | Exploratory, usability, A/B |
| 象限 | 目标 | 示例 |
|---|---|---|
| 技术+支持 | 快速反馈 | 单元测试、组件测试、集成测试 |
| 技术+评估 | 探索系统极限 | 性能测试、安全测试、混沌测试 |
| 业务+支持 | 达成共识 | BDD、验收测试 |
| 业务+评估 | 发现未知问题 | 探索性测试、可用性测试、A/B测试 |
Agent Selection by PACT + Quadrant
基于PACT+象限的Agent选择
| PACT Dimension | Agents |
|---|---|
| Proactive + Tech | qe-test-generator, qe-requirements-validator |
| Autonomous + Tech | qe-test-executor, qe-coverage-analyzer |
| Collaborative | qe-fleet-commander (orchestration) |
| Targeted | qe-regression-risk-analyzer, qe-quality-gate |
| PACT维度 | 对应Agent |
|---|---|
| 前瞻性+技术 | qe-test-generator, qe-requirements-validator |
| 自主性+技术 | qe-test-executor, qe-coverage-analyzer |
| 协作性 | qe-fleet-commander（编排） |
| 针对性 | qe-regression-risk-analyzer, qe-quality-gate |
PACT in Practice
PACT实践案例
Proactive: Test Before Bugs
前瞻性：在bug出现前测试
javascript
// During API design, ask: "How will we know if this times out under load?"
// Build observability from start
await Task("Risk Analysis", {
phase: 'refinement',
question: 'What could go wrong and how will we know?'
}, "qe-requirements-validator");javascript
// 在API设计阶段，思考：“我们如何知晓它在负载下是否会超时？”
// 从一开始就构建可观测性
await Task("Risk Analysis", {
phase: 'refinement',
question: 'What could go wrong and how will we know?'
}, "qe-requirements-validator");Autonomous: Teams Own Quality
自主性：团队对质量负责
- Developers run full test suite locally
- CI fails fast with clear diagnostics
- No manual deployment approvals
- Self-service test environments
- 开发者本地运行完整测试套件
- CI流水线快速失败并提供清晰诊断信息
- 无人工部署审批环节
- 自助式测试环境
Collaborative: Whole-Team Thinking
协作性：全员质量思维
- QE attends planning and refinement
- Three Amigos for every user story
- Shared ownership of test code
- Ensemble testing for complex scenarios
- QA参与规划和需求细化会议
- 每个用户故事都开展三方协作（业务、开发、测试）
- 测试代码所有权共享
- 复杂场景采用团队协作测试
Targeted: Test What Matters
针对性：测试关键内容
javascript
// E-commerce checkout? Test thoroughly.
// Admin panel used twice a month? Lighter touch.
await Task("Risk-Based Planning", {
critical: ['checkout', 'payment'],
light: ['admin-panel', 'settings']
}, "qe-regression-risk-analyzer");javascript
// 电商结账流程？全面测试。
// 每月仅使用两次的管理面板？轻量化测试。
await Task("Risk-Based Planning", {
critical: ['checkout', 'payment'],
light: ['admin-panel', 'settings']
}, "qe-regression-risk-analyzer");Evolution from Traditional
与传统模式的对比
| Old Way (Sequential) | Holistic + PACT (Concurrent) |
|---|---|
| Dev writes → QA tests → bugs found → fixes | Team discusses what to build and how to test |
| Slow feedback, finger-pointing | Fast feedback, shared ownership |
| Quality as gatekeeping | Quality as enabler |
| QA on critical path | QA builds infrastructure, coaches |
| 旧模式（串行） | 整体测试+PACT模式（并行） |
|---|---|
| 开发编码 → QA测试 → 发现bug → 修复 | 团队共同讨论要构建的内容及测试方式 |
| 反馈缓慢，互相推诿 | 快速反馈，共享所有权 |
| 质量是守门员角色 | 质量是赋能角色 |
| QA处于关键路径 | QA搭建基础设施、提供指导 |
Success Signals
成功标志
- Features deploy multiple times per day
- Bug escape rate trending down
- Team discusses quality naturally
- Developers write tests without being told
- Releases are boring (in a good way)
- 功能每天可多次部署
- bug逃逸率持续下降
- 团队自然讨论质量话题
- 开发者主动编写测试用例
- 发布流程平稳无意外（理想状态）
Agent Coordination Hints
Agent协调提示
Memory Namespace
内存命名空间
aqe/holistic-testing/
├── pact-assessment/* - PACT maturity analysis
├── quadrant-coverage/* - Coverage per quadrant
├── team-metrics/* - Quality ownership metrics
└── feedback-loops/* - Cycle time dataaqe/holistic-testing/
├── pact-assessment/* - PACT成熟度分析
├── quadrant-coverage/* - 象限覆盖情况
├── team-metrics/* - 质量所有权指标
└── feedback-loops/* - 周期时间数据Fleet Coordination
集群协调
typescript
const holisticFleet = await FleetManager.coordinate({
strategy: 'holistic-testing',
pact: { proactive: true, autonomous: true, collaborative: true, targeted: true },
agents: [
'qe-fleet-commander', // Orchestration
'qe-test-generator', // Tech quadrant
'qe-requirements-validator', // Business quadrant
'qe-quality-analyzer' // Metrics
],
topology: 'mesh'
});typescript
const holisticFleet = await FleetManager.coordinate({
strategy: 'holistic-testing',
pact: { proactive: true, autonomous: true, collaborative: true, targeted: true },
agents: [
'qe-fleet-commander', // Orchestration
'qe-test-generator', // Tech quadrant
'qe-requirements-validator', // Business quadrant
'qe-quality-analyzer' // Metrics
],
topology: 'mesh'
});Related Skills
相关技能
- agentic-quality-engineering - Agent coordination
- context-driven-testing - Adapt to context
- shift-left-testing - Proactive testing
- risk-based-testing - Targeted testing
- agentic-quality-engineering - Agent协调
- context-driven-testing - 适配场景
- shift-left-testing - 左移测试
- risk-based-testing - 基于风险的测试
Remember
要点回顾
PACT = Proactive + Autonomous + Collaborative + Targeted
Quality is built in, not tested in. Teams own quality. QA enables, doesn't gate. Test what matters, skip what doesn't. Measure outcomes, not activities.
With Agents: Agents analyze PACT maturity, recommend quadrant coverage, and coordinate whole-team quality. Use agents to scale holistic thinking while maintaining human judgment.
PACT = 前瞻性 + 自主性 + 协作性 + 针对性
质量是构建出来的，而非测试出来的。团队对质量负责。QA是赋能者，而非守门员。测试关键内容，忽略无价值部分。衡量结果，而非活动。
Agent的价值： Agent可分析PACT成熟度、推荐象限覆盖策略、协调全员质量实践。借助Agent可规模化落地整体测试思维，同时保留人工判断。