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.
Instrucciones de origen · Vista previa de solo lectura
name
holistic-testing-pact
description
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.
// During API design, ask: "How will we know if this times out under load?"// Build observability from startawaitTask("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.awaitTask("Risk-Based Planning", {
critical: ['checkout', 'payment'],
light: ['admin-panel', 'settings']
}, "qe-regression-risk-analyzer");
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 boxawaitTask("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 be trustworthy 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
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/
├── pacts-assessment/* - PACTS maturity analysis
├── quadrant-coverage/* - Coverage per quadrant
├── team-metrics/* - Quality ownership metrics
└── feedback-loops/* - Cycle time data
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.
