Holistic Testing Model with PACT Principles
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
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
PACT Principles
| 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 |
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 |
Agent Selection by PACT + Quadrant
| 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 in Practice
Proactive: Test Before Bugs
// 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");
Autonomous: Teams Own Quality
- Developers run full test suite locally
- CI fails fast with clear diagnostics
- No manual deployment approvals
- Self-service test environments
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
Targeted: Test What Matters
// 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");
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 |
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)
Agent Coordination Hints
Memory Namespace
aqe/holistic-testing/
├── pact-assessment/* - PACT maturity analysis
├── quadrant-coverage/* - Coverage per quadrant
├── team-metrics/* - Quality ownership metrics
└── feedback-loops/* - Cycle time data
Fleet Coordination
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
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.
1---2name: holistic-testing-pact3description: Apply the Holistic Testing Model evolved with PACT (Proactive, Autonomous, Collaborative, Targeted) principles. Use when designing comprehensive test strategies for Classical, AI-assisted, Agent based, or Agentic Systems building quality into the team, or implementing whole-team quality practices.4---56# Holistic Testing Model with PACT Principles78<default_to_action>9When designing test strategies or building quality into teams:101. APPLY PACT principles: Proactive (test before bugs), Autonomous (teams own quality), Collaborative (whole-team responsibility), Targeted (risk-focused)112. IDENTIFY quadrant focus: Technology-facing (unit, integration, performance) or Business-facing (acceptance, exploratory, usability)123. SELECT agents based on PACT dimension and testing quadrant134. IMPLEMENT feedback loops that catch issues in minutes, not days145. MEASURE outcomes (bug escape rate, release confidence) not activities (test count)1516**Quick PACT Application:**17- Proactive → Design testability into architecture, risk analysis during refinement18- Autonomous → Devs run tests locally, CI pipeline with no manual gates19- Collaborative → Three Amigos, QE pairs with dev, shared test ownership20- Targeted → Risk-based planning, focus on critical flows, kill valueless tests2122**Critical Success Factors:**23- Quality is a whole-team responsibility, not a QA phase24- QA as enablers (build infrastructure, coach), not gatekeepers25- Fast feedback during development, not after26</default_to_action>2728## Quick Reference Card2930### When to Use31- Designing comprehensive test strategies32- Building quality culture in teams33- Choosing testing approach for new projects34- Evolving from sequential QA to concurrent quality3536### PACT Principles37| Principle | Focus | Anti-Pattern |38|-----------|-------|--------------|39| **Proactive** | Test before code, design testability | Waiting for bugs to find you |40| **Autonomous** | Teams deploy when ready | QA as manual gatekeepers |41| **Collaborative** | Whole-team quality thinking | QA works in isolation |42| **Targeted** | Risk-based, high-value tests | Exhaustive checkbox testing |4344### Holistic Testing Quadrants45| Quadrant | Purpose | Examples |46|----------|---------|----------|47| Tech + Support | Fast feedback | Unit, component, integration tests |48| Tech + Critique | Find limits | Performance, security, chaos |49| Business + Support | Shared understanding | BDD, acceptance tests |50| Business + Critique | Discover unknowns | Exploratory, usability, A/B |5152### Agent Selection by PACT + Quadrant53| PACT Dimension | Agents |54|----------------|--------|55| Proactive + Tech | qe-test-generator, qe-requirements-validator |56| Autonomous + Tech | qe-test-executor, qe-coverage-analyzer |57| Collaborative | qe-fleet-commander (orchestration) |58| Targeted | qe-regression-risk-analyzer, qe-quality-gate |5960---6162## PACT in Practice6364### Proactive: Test Before Bugs65```javascript66// During API design, ask: "How will we know if this times out under load?"67// Build observability from start68await Task("Risk Analysis", {69 phase: 'refinement',70 question: 'What could go wrong and how will we know?'71}, "qe-requirements-validator");72```7374### Autonomous: Teams Own Quality75- Developers run full test suite locally76- CI fails fast with clear diagnostics77- No manual deployment approvals78- Self-service test environments7980### Collaborative: Whole-Team Thinking81- QE attends planning and refinement82- Three Amigos for every user story83- Shared ownership of test code84- Ensemble testing for complex scenarios8586### Targeted: Test What Matters87```javascript88// E-commerce checkout? Test thoroughly.89// Admin panel used twice a month? Lighter touch.90await Task("Risk-Based Planning", {91 critical: ['checkout', 'payment'],92 light: ['admin-panel', 'settings']93}, "qe-regression-risk-analyzer");94```9596---9798## Evolution from Traditional99100| Old Way (Sequential) | Holistic + PACT (Concurrent) |101|---------------------|------------------------------|102| Dev writes → QA tests → bugs found → fixes | Team discusses what to build and how to test |103| Slow feedback, finger-pointing | Fast feedback, shared ownership |104| Quality as gatekeeping | Quality as enabler |105| QA on critical path | QA builds infrastructure, coaches |106107---108109## Success Signals110111- Features deploy multiple times per day112- Bug escape rate trending down113- Team discusses quality naturally114- Developers write tests without being told115- Releases are boring (in a good way)116117---118119## Agent Coordination Hints120121### Memory Namespace122```123aqe/holistic-testing/124├── pact-assessment/* - PACT maturity analysis125├── quadrant-coverage/* - Coverage per quadrant126├── team-metrics/* - Quality ownership metrics127└── feedback-loops/* - Cycle time data128```129130### Fleet Coordination131```typescript132const holisticFleet = await FleetManager.coordinate({133 strategy: 'holistic-testing',134 pact: { proactive: true, autonomous: true, collaborative: true, targeted: true },135 agents: [136 'qe-fleet-commander', // Orchestration137 'qe-test-generator', // Tech quadrant138 'qe-requirements-validator', // Business quadrant139 'qe-quality-analyzer' // Metrics140 ],141 topology: 'mesh'142});143```144145---146147## Related Skills148- [agentic-quality-engineering](../agentic-quality-engineering/) - Agent coordination149- [context-driven-testing](../context-driven-testing/) - Adapt to context150- [shift-left-testing](../shift-left-testing/) - Proactive testing151- [risk-based-testing](../risk-based-testing/) - Targeted testing152153---154155## Remember156157**PACT = Proactive + Autonomous + Collaborative + Targeted**158159Quality 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.160161**With Agents:** Agents analyze PACT maturity, recommend quadrant coverage, and coordinate whole-team quality. Use agents to scale holistic thinking while maintaining human judgment.
fndlalit