⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

agent-integration-testing

av@av⭐ 28 stars· last commit 4d ago· 0 open issues

Use when the user requests integration testing, feature validation, or test plan execution

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 28 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

agent-integration-testing

Use when the user requests integration testing, feature validation, or test plan execution

npx skills add av/skills --skill agent-integration-testing

Part of av/skills — a library of agent skills for Claude Code, Codex, OpenCode and other coding agents.

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • agent-integration-testing/SKILL.md3.5 KBupstream ↗
    ---
    name: agent-integration-testing
    description: Use when the user requests integration testing, feature validation, or test plan execution
    ---
    
    # Agent Integration Testing
    
    ## Overview
    This skill guides the creation and autonomous execution of verifiable integration test specifications. It ensures that tests are actionable by agents, properly documented, and systematically executed by subagents to validate features or fix failures.
    
    ## Core Process
    
    1. **Investigate Codebase Area**
       - By default, investigate the entire codebase to understand the context.
       - If the user specifies a feature area, use `glob` and `grep` to narrow the investigation.
    
    2. **Write Test Specification**
       - Create a test spec file at `./tests/<name>.md`.
       - Use `<name> = "integration"` unless the user specifies a particular feature area.
       - The document MUST include a **Prerequisites** section at the top detailing any setup needed before tests become runnable (e.g., environment variables, database seeding, background services).
    
    3. **Define Verifiable Tests**
       - Each test must be written in plain English.
       - Include clear **steps to reproduce**.
       - Include a set of **expectations**.
       - **CRITICAL:** Every expectation must be strictly verifiable by an agent using available tools (e.g., shell commands, HTTP requests, reading file outputs). If a test cannot be verified by an agent, it is invalid and must be rewritten or removed.
    
    4. **Execute Tests via Subagents**
       - Spawn subagents (using the `Task` tool or `@mention` subagent system) to run each individual test.
       - The subagent must follow the prerequisites, execute the steps, and validate the outcomes against the expectations.
       - Collect the results (Pass/Fail and logs) from the subagents.
    
    5. **Fix Failures (Optional)**
       - If the user explicitly specifies that failures should be fixed, spawn another subagent (e.g., the `SWE` or `BUILDER` agent) to investigate and fix any noted failures.
    
    ## Quick Reference
    
    | Action | Pattern / Command |
    |--------|-------------------|
    | Test File Location | `./tests/<name>.md` (default: `integration.md`) |
    | Prerequisites | Must be documented at the top of the test file |
    | Test Format | Plain English, Repro Steps, Verifiable Expectations |
    | Execution | Spawn one subagent per test or test suite |
    | Fixing | Spawn SWE/BUILDER subagent if requested by user |
    
    ## Red Flags - STOP and Start Over
    
    - **Unverifiable Tests:** "Verify the UI looks nice" or "Check if the animation is smooth." (Agents cannot verify visual aesthetics without specific tools). **Fix:** Rewrite to check DOM elements, network responses, or file states.
    - **Missing Prerequisites:** Subagents failing because the server wasn't started. **Fix:** Ensure the prerequisite section explicitly defines the commands to start dependencies.
    - **Executing Tests Manually:** Running tests in the main conversation thread instead of spawning subagents. **Fix:** Dispatch parallel subagents for isolated execution.
    
    ## Example Test Specification (`./tests/auth-integration.md`)
    
    ```markdown
    # Auth Integration Tests
    
    ## Prerequisites
    - Start the test database: `docker compose up -d db`
    - Run migrations: `npm run migrate`
    - Start the server in background: `npm run start:test &`
    
    ## Test 1: User Registration
    **Steps:**
    1. Send a POST request to `/api/register` with payload `{"email": "[email protected]", "password": "pass"}`.
    
    **Expectations:**
    1. The HTTP response status must be `201 Created`.
    2. A subsequent query to the database using `sqlite3 test.db "SELECT email FROM users WHERE email='[email protected]';"` must return the email.
    ```
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/av-skills-agent-integration-testing.md

// REPO STATS

28 stars
0 open issues
Last commit: 4d ago