agentleFS
irahardiantoirahardianto/awesome-agv/.agents/skills/test-integration/SKILL.md

test-integration

Skill157 starsChanged 33 days agoMITView on GitHub

Audits I/O adapters, sets up test infrastructure, and systematically improves integration test coverage. User-invoked entry point via /test-integration; not for autonomous or subagent use.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After discovering adapter bugs in production

    line 19
  2. Distinctive:

    Create shared test infrastructure setup (reusable across tests): container lifecycle, seed data scripts, connection factory for test …

    line 46
  3. Very specific:

    If CI pipeline exists, verify integration tests can run in CI (reference ci-cd skill)

    line 47
  4. Distinctive:

    Gate: Test infrastructure running.

    line 51
  5. Distinctive:

    Objective: Write integration tests for each uncovered adapter.

    line 54
  6. Very specific:

    Use testability-patterns skill for adapter test structure

    line 61
  7. Distinctive:

    Ensure test isolation — each test manages its own state (setup + teardown)

    line 62
  8. Distinctive:

    Gate: All adapter integration tests pass against real infrastructure.

    line 66
  9. Distinctive:

    Run all integration tests end-to-end

    line 71
  10. Distinctive:

    Verify tests run in CI pipeline (if applicable)

    line 73
  11. Distinctive:

    Run quality checks per idiom skill

    line 74
  12. Distinctive:

    Gate: All integration tests pass.

    line 76

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Improve Integration Test Coverage

Entry-point guard: This is a user-invoked command skill (/test-integration). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.

Purpose

Audit and improve integration test coverage for I/O adapters. For unit test gaps, use the /test-unit skill.

When to Use

  • I/O adapters (database, HTTP clients, file system, message queues) lack integration tests
  • New infrastructure components without integration tests
  • Pre-release verification of adapter reliability
  • After discovering adapter bugs in production

When NOT to Use

  • Unit test gaps (use /test-unit skill)
  • E2E test gaps (use /test-e2e skill)
  • New feature development (use /workflow-solo)

Phases

Phase 1: AUDIT

Objective: Map which adapters have integration tests and which don't.

  1. Scan codebase for I/O adapter patterns per @architectural-pattern.md: search for Repository, Store, Client, Adapter, Gateway, Provider in type/interface names. Also search for database drivers, HTTP clients, file system operations, message queue connections.
  2. For each discovered adapter, check for corresponding integration test file. Language-specific naming conventions come from the idiom skill (e.g., Go: *_integration_test.go, TS: *.integration.spec.ts, Python: *_integration_test.py)
  3. Produce Adapter Coverage Map artifact: adapter name, type (DB/HTTP/FS/Queue), has integration test (Y/N), test file path if exists

Gate: Adapter coverage map created. All I/O boundaries identified.

Phase 2: INFRASTRUCTURE

Objective: Set up test infrastructure for untested adapters.

  1. Load testing-strategy skill for Testcontainers and infrastructure patterns
  2. For each untested adapter, set up required infrastructure:
    • Database adapters: Testcontainers with target database
    • HTTP client adapters: Mock server or test endpoint
    • File system adapters: Temp directory with cleanup
    • Message queue adapters: Testcontainers with target broker
  3. Create shared test infrastructure setup (reusable across tests): container lifecycle, seed data scripts, connection factory for test environments
  4. If CI pipeline exists, verify integration tests can run in CI (reference ci-cd skill)

Skills to consider: testing-strategy, ci-cd

Gate: Test infrastructure running. Containers start and connect successfully.

Phase 3: TEST

Objective: Write integration tests for each uncovered adapter.

  1. For each untested adapter from the audit: a. Test contract compliance — verify adapter implements its interface correctly against real infrastructure b. Test CRUD operations (where applicable) c. Test error handling — connection failures, timeouts, invalid data d. Test edge cases — empty results, large payloads, concurrent access
  2. Use testability-patterns skill for adapter test structure
  3. Ensure test isolation — each test manages its own state (setup + teardown)

Skills to consider: testability-patterns

Gate: All adapter integration tests pass against real infrastructure.

Phase 4: VERIFY

Objective: Confirm coverage and CI readiness.

  1. Run all integration tests end-to-end
  2. Report: adapters tested vs total adapters (before/after)
  3. Verify tests run in CI pipeline (if applicable)
  4. Run quality checks per idiom skill

Gate: All integration tests pass. Adapter coverage improved. CI pipeline updated if applicable.

Completion Criteria

  • Adapter coverage map created
  • Test infrastructure configured and running
  • Integration tests written for all uncovered adapters
  • All integration tests pass against real infrastructure
  • Adapter coverage report generated (before vs after)
  • CI pipeline runs integration tests (if applicable)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.