Holistic Testing Model with PACT Principles

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

1. APPLY PACT principles: Proactive (test before bugs), Autonomous (teams own quality), Collaborative (whole-team responsibility), Targeted (risk-focused)
2. IDENTIFY quadrant focus: Technology-facing (unit, integration, performance) or Business-facing (acceptance, exploratory, usability)
3. SELECT agents based on PACT dimension and testing quadrant
4. IMPLEMENT feedback loops that catch issues in minutes, not days
5. MEASURE outcomes (bug escape rate, release confidence) not activities (test count)

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

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

PACT Principles

Holistic Testing Quadrants

Agent Selection by PACT + Quadrant

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

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

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

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.