testing-boss

Enforce behavior-focused invariants and anti-flakiness rules when authoring or reviewing tests.

182|8|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/compozy/agh --skill testing-boss
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-boss
Source: https://github.com/compozy/agh/tree/main/.agents/skills/testing-boss
Command: npx skills add https://github.com/compozy/agh --skill testing-boss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Testing doctrine that helps you write tests (including agent-generated tests) that fail for the right reason, avoid common brittleness and flakiness traps, and ensure CI gates real regressions instead of producing decorative green.

Core Features & Use Cases

  • Behavior-first test design: Uses practical invariants, clear boundaries, and resilient selector/assertion strategies to ensure tests protect what users actually experience.
  • Flaky/fragile suite prevention: Provides a taxonomy of flaky test causes (timing, order/state pollution, concurrency, nondeterminism) plus workflows like quarantine with owners and fix-by dates.
  • Agent safety gates for test generation: Enforces seven gates (invariant first, owning layer, real execution, failure→fix production, no snapshot without contract, no assertion on self-set mock, negative companion) to stop agents from gaming tests via mocks, snapshots, or happy-path-only coverage.
  • LLM/agent eval alignment: Connects conventional test rigor to probabilistic LLM oracles with an oracle ladder and eval-dataset principles.

Quick Start

Ask an AI assistant to review or generate your next test for a specific bug by requiring it to state the INVARIANT and OWNING_LAYER first, then check for a negative companion and real execution before providing any test code.

Frequently Asked Questions about testing-boss

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

FAQPage Schema
How do I prevent flaky tests in my CI pipeline?▼

Prevent flaky tests by applying a taxonomy of causes like timing, state pollution, and nondeterminism, then enforcing workflows that mandate quarantine with assigned owners and strict fix-by dates to stabilize CI gates.

How do I stop coding agents from generating mock-driven tests?▼

Stop agent-generated mock misuse by enforcing safety gates that forbid assertions on self-set mock values, require invariant-first design, and mandate real-system execution to prevent hollow, mock-driven confidence in test suites.

What is the best way to design tests that fail for the right reason?▼

Design tests that fail correctly by defining behavior-focused invariants and selecting the owning layer first, ensuring your assertions protect actual user experiences rather than internal implementation details.

How do I build eval suites for LLM agents?▼

Build LLM agent eval suites by applying an oracle ladder and eval-dataset principles, connecting conventional test rigor to probabilistic LLM oracles to accurately evaluate agent behavior and performance.

Why do my integration tests pass but regressions still reach production?▼

Integration tests often pass but miss regressions due to happy-path-only coverage; enforcing negative companion tests and real execution ensures CI gates catch actual behavioral failures instead of producing decorative green.

When should I use snapshots in test design?▼

Use snapshots in test design only when classified as contracts rather than implementation details, ensuring they verify stable interfaces without becoming brittle fixtures that break during harmless refactoring.