qa-testers

Enforce ZERO MOCK testing across BaseAgent implementations and audit CLI verification.

Updated Mar 5, 2026

Search Tags:#test-automation #qa-testing #policy-validation #zero-mocks #swarm-testing #audit-cli

Ready to run

npx skills add https://github.com/ShubhamManachekar/GeoSupply --skill qa-testers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-testers
Source: https://github.com/ShubhamManachekar/GeoSupply/tree/main/.agent/skills/qa-testers
Command: npx skills add https://github.com/ShubhamManachekar/GeoSupply --skill qa-testers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GeoSupply QA testers enforce strict testing boundaries to verify multi-agent system behavior under the ZERO MOCKS policy.

Core Features & Use Cases

Zero-mock enforcement: ensures real components are tested without patching, across BaseAgent implementations and the audit CLI.
Phase-aware QA: validates transitions and error handling in the agent state machine, with explicit invalid transition testing.
Cross-phase auditing: ensures audit CLI flags are exercised by tests and enforces fail-fast behavior if core abstractions are not overridden.

Quick Start

Run the QA test suite against a live swarm deployment to verify ZERO MOCK policy enforcement.

Frequently Asked Questions about qa-testers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a zero mocks policy in multi-agent test automation?▼

A zero mocks policy in test automation enforces strict testing boundaries by verifying multi-agent system behavior with real components rather than using patches or mocks. This approach validates actual BaseAgent implementations and state-machine transitions without simulated dependencies.

How do I validate state-machine transitions in a multi-agent swarm deployment?▼

To validate state-machine transitions in a multi-agent swarm deployment, apply phase-aware QA checks that test explicit invalid transitions and error handling. This ensures agents fail-fast if core abstractions are not properly overridden during execution.

Does the zero mocks testing approach work with audit CLI verification?▼

Yes, the zero mocks testing approach integrates directly with audit CLI verification. It ensures that all audit CLI flags are actively exercised by tests and enforces fail-fast behavior if required core abstractions are not overridden.

How do I run a QA test suite against a live swarm deployment?▼

To run QA tests against a live swarm deployment, execute the test suite to verify zero mock policy enforcement across components. This validates environment handling, patch avoidance, and deterministic behavior across BaseAgent implementations and audit CLI checks.

What are the limitations of enforcing zero mocks across multi-agent components?▼

The primary limitation of enforcing zero mocks is that all testing must execute against live components and real state-machine transitions. It requires strict environment handling and fails immediately if core abstractions are not overridden, preventing partial or isolated test execution.