/holistic-testing-pact

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."
category: testing-methodologies
priority: critical
tokenEstimate: 1100
agents: [qe-fleet-commander, qe-test-generator, qe-quality-analyzer, qe-requirements-validator]
implementation_status: optimized
optimization_version: 1.0
last_optimized: 2025-12-02
dependencies: []
quick_reference_card: true
tags: [holistic, pacts, quality, whole-team, proactive, autonomous, collaborative, targeted, structured]
trust_tier: 0
validation:

Holistic Testing Model with PACTS Principles

<default_to_action> 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

</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

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
• 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 exp