Holistic Testing Model with PACTS Principles
Quick PACTS Application:
- Proactive → Design testability into architecture, risk analysis during refinement
- Autonomous → Devs run tests locally, CI gates automated wherever risk and regulation allow
- Collaborative → Three Amigos, QE pairs with dev, shared test ownership
- Targeted → Risk-based planning, focus on critical flows, kill valueless tests
- Structured → Governance, observability, and explainability of agent behavior; measure confidence, not trust
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
PACTS 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 |
| Structured |
Governance, observability, explainability of agent behavior |
Bolting agentic AI onto chaos |
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 PACTS + Quadrant
| PACTS 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 |
| Structured |
qe-fleet-commander, qe-quality-gate (governance, observability, explainability) |
PACTS 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
- Deployment approvals automated where the risk allows; where regulation or risk requires a human sign-off, make it fast and evidence-based rather than a queue
- 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");
Structured: Governance, Observability, Explainability
The 5th principle for agentic systems. As agents take on quality work, you need
governance (boundaries and guardrails), observability (what agents did and why),
and explainability (decisions you can audit). Especially important in regulated
industries.
- We measure CONFIDENCE, not trust — trust is a human feeling; confidence can
be mathematically explained.
- Ships with a playbook + readiness-assessment guide.
- Anti-pattern: bolting agentic AI onto chaos. Structure first, then automate.
// Make agent behavior auditable and explainable, not a black box
await Task("Agent Governance Review", {
guardrails: ['scope-boundaries', 'approval-gates'],
observability: ['decision-traces', 'confidence-scores'],
explainability: 'every-decision-auditable'
}, "qe-fleet-commander");
From PACT to PACTS
PACT originated with Reuven Cohen (Agentics Foundation) and was adapted to quality
engineering by Dragan Spiridonov. PACTS adds a fifth principle — Structured —
inspired by DORA's research on AI-assisted delivery and platform-engineering
quality measurement. The addition reflects that autonomous, agentic quality work
needs governance, observability, and explainability to earn confidence at scale.
Evolution from Traditional
| Old Way (Sequential) |
Holistic + PACTS (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
- Deployments happen as often as the business and its risk profile need, without fear (a medical device and a consumer web app have different right answers)
- 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/
├── pacts-assessment/* - PACTS 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',
pacts: { proactive: true, autonomous: true, collaborative: true, targeted: true, structured: 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
PACTS = Proactive + Autonomous + Collaborative + Targeted + Structured
Quality is built in, not tested in. Teams own quality. QA enables, doesn't gate. Test what matters, skip what doesn't. Govern agent behavior with observability and explainability — measure confidence, not trust. Measure outcomes, not activities.
With Agents: Agents analyze PACTS maturity, recommend quadrant coverage, and coordinate whole-team quality. Use agents to scale holistic thinking while maintaining human judgment.
1---2inclusion: auto3name: qe-holistic-testing-pact4description: "Apply the Holistic Testing Model evolved with PACTS (Proactive, Autonomous, Collaborative, Targeted, Structured) 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."5tags: [holistic, pacts, quality, whole-team, proactive, autonomous, collaborative, targeted, structured]6metadata:7 source: https://skillmd.com/skills/proffesor-for-testing/qe-holistic-testing-pact8---910# Holistic Testing Model with PACTS Principles1112<default_to_action>13When designing test strategies or building quality into teams:141. APPLY PACTS principles: Proactive (test before bugs), Autonomous (teams own quality), Collaborative (whole-team responsibility), Targeted (risk-focused), Structured (governance, observability, and explainability of agent behavior)152. IDENTIFY quadrant focus: Technology-facing (unit, integration, performance) or Business-facing (acceptance, exploratory, usability)163. SELECT agents based on PACTS dimension and testing quadrant174. IMPLEMENT feedback loops that catch issues in minutes, not days185. MEASURE outcomes (bug escape rate, release confidence, agent confidence) not activities (test count)1920**Quick PACTS Application:**21- Proactive → Design testability into architecture, risk analysis during refinement22- Autonomous → Devs run tests locally, CI gates automated wherever risk and regulation allow23- Collaborative → Three Amigos, QE pairs with dev, shared test ownership24- Targeted → Risk-based planning, focus on critical flows, kill valueless tests25- Structured → Governance, observability, and explainability of agent behavior; measure confidence, not trust2627**Critical Success Factors:**28- Quality is a whole-team responsibility, not a QA phase29- QA as enablers (build infrastructure, coach), not gatekeepers30- Fast feedback during development, not after31</default_to_action>3233## Quick Reference Card3435### When to Use36- Designing comprehensive test strategies37- Building quality culture in teams38- Choosing testing approach for new projects39- Evolving from sequential QA to concurrent quality4041### PACTS Principles42| Principle | Focus | Anti-Pattern |43|-----------|-------|--------------|44| **Proactive** | Test before code, design testability | Waiting for bugs to find you |45| **Autonomous** | Teams deploy when ready | QA as manual gatekeepers |46| **Collaborative** | Whole-team quality thinking | QA works in isolation |47| **Targeted** | Risk-based, high-value tests | Exhaustive checkbox testing |48| **Structured** | Governance, observability, explainability of agent behavior | Bolting agentic AI onto chaos |4950### Holistic Testing Quadrants51| Quadrant | Purpose | Examples |52|----------|---------|----------|53| Tech + Support | Fast feedback | Unit, component, integration tests |54| Tech + Critique | Find limits | Performance, security, chaos |55| Business + Support | Shared understanding | BDD, acceptance tests |56| Business + Critique | Discover unknowns | Exploratory, usability, A/B |5758### Agent Selection by PACTS + Quadrant59| PACTS Dimension | Agents |60|----------------|--------|61| Proactive + Tech | qe-test-generator, qe-requirements-validator |62| Autonomous + Tech | qe-test-executor, qe-coverage-analyzer |63| Collaborative | qe-fleet-commander (orchestration) |64| Targeted | qe-regression-risk-analyzer, qe-quality-gate |65| Structured | qe-fleet-commander, qe-quality-gate (governance, observability, explainability) |6667---6869## PACTS in Practice7071### Proactive: Test Before Bugs72```javascript73// During API design, ask: "How will we know if this times out under load?"74// Build observability from start75await Task("Risk Analysis", {76 phase: 'refinement',77 question: 'What could go wrong and how will we know?'78}, "qe-requirements-validator");79```8081### Autonomous: Teams Own Quality82- Developers run full test suite locally83- CI fails fast with clear diagnostics84- Deployment approvals automated where the risk allows; where regulation or risk requires a human sign-off, make it fast and evidence-based rather than a queue85- Self-service test environments8687### Collaborative: Whole-Team Thinking88- QE attends planning and refinement89- Three Amigos for every user story90- Shared ownership of test code91- Ensemble testing for complex scenarios9293### Targeted: Test What Matters94```javascript95// E-commerce checkout? Test thoroughly.96// Admin panel used twice a month? Lighter touch.97await Task("Risk-Based Planning", {98 critical: ['checkout', 'payment'],99 light: ['admin-panel', 'settings']100}, "qe-regression-risk-analyzer");101```102103### Structured: Governance, Observability, Explainability104The 5th principle for agentic systems. As agents take on quality work, you need105governance (boundaries and guardrails), observability (what agents did and why),106and explainability (decisions you can audit). Especially important in regulated107industries.108109- We measure **CONFIDENCE, not trust** — trust is a human feeling; confidence can110 be mathematically explained.111- Ships with a playbook + readiness-assessment guide.112- Anti-pattern: bolting agentic AI onto chaos. Structure first, then automate.113114```javascript115// Make agent behavior auditable and explainable, not a black box116await Task("Agent Governance Review", {117 guardrails: ['scope-boundaries', 'approval-gates'],118 observability: ['decision-traces', 'confidence-scores'],119 explainability: 'every-decision-auditable'120}, "qe-fleet-commander");121```122123---124125## From PACT to PACTS126127PACT originated with Reuven Cohen (Agentics Foundation) and was adapted to quality128engineering by Dragan Spiridonov. PACTS adds a fifth principle — **Structured** —129inspired by DORA's research on AI-assisted delivery and platform-engineering130quality measurement. The addition reflects that autonomous, agentic quality work131needs governance, observability, and explainability to earn confidence at scale.132133---134135## Evolution from Traditional136137| Old Way (Sequential) | Holistic + PACTS (Concurrent) |138|---------------------|------------------------------|139| Dev writes → QA tests → bugs found → fixes | Team discusses what to build and how to test |140| Slow feedback, finger-pointing | Fast feedback, shared ownership |141| Quality as gatekeeping | Quality as enabler |142| QA on critical path | QA builds infrastructure, coaches |143144---145146## Success Signals147148- Deployments happen as often as the business and its risk profile need, without fear (a medical device and a consumer web app have different right answers)149- Bug escape rate trending down150- Team discusses quality naturally151- Developers write tests without being told152- Releases are boring (in a good way)153154---155156## Agent Coordination Hints157158### Memory Namespace159```160aqe/holistic-testing/161├── pacts-assessment/* - PACTS maturity analysis162├── quadrant-coverage/* - Coverage per quadrant163├── team-metrics/* - Quality ownership metrics164└── feedback-loops/* - Cycle time data165```166167### Fleet Coordination168```typescript169const holisticFleet = await FleetManager.coordinate({170 strategy: 'holistic-testing',171 pacts: { proactive: true, autonomous: true, collaborative: true, targeted: true, structured: true },172 agents: [173 'qe-fleet-commander', // Orchestration174 'qe-test-generator', // Tech quadrant175 'qe-requirements-validator', // Business quadrant176 'qe-quality-analyzer' // Metrics177 ],178 topology: 'mesh'179});180```181182---183184## Related Skills185- [agentic-quality-engineering](../agentic-quality-engineering/) - Agent coordination186- [context-driven-testing](../context-driven-testing/) - Adapt to context187- [shift-left-testing](../shift-left-testing/) - Proactive testing188- [risk-based-testing](../risk-based-testing/) - Targeted testing189190---191192## Remember193194**PACTS = Proactive + Autonomous + Collaborative + Targeted + Structured**195196Quality is built in, not tested in. Teams own quality. QA enables, doesn't gate. Test what matters, skip what doesn't. Govern agent behavior with observability and explainability — measure confidence, not trust. Measure outcomes, not activities.197198**With Agents:** Agents analyze PACTS maturity, recommend quadrant coverage, and coordinate whole-team quality. Use agents to scale holistic thinking while maintaining human judgment.