Holistic Testing Model with PACTS Principles

<defaulttoaction> When designing test strategies or building quality into teams:

1. 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)
2. IDENTIFY quadrant focus: Technology-facing (unit, integration, performance) or Business-facing (acceptance, exploratory, usability)
3. SELECT agents based on PACTS dimension and testing quadrant
4. IMPLEMENT feedback loops that catch issues in minutes, not days
5. MEASURE outcomes (bug escape rate, release confidence, agent confidence) not activities (test count)

Quick PACTS 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
• 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

</defaulttoaction>

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

Holistic Testing Quadrants

Agent Selection by PACTS + Quadrant

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
• 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");

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 be trustworthy at scale.

Evolution from Traditional

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

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

• [agentic-quality-engineering](../agentic-quality-engineering/) - Agent coordination
• [context-driven-testing](../context-driven-testing/) - Adapt to context
• [shift-left-testing](../shift-left-testing/) - Proactive testing
• [risk-based-testing](../risk-based-testing/) - Targeted testing

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.