Integration Test Design

Testing multiple components together; contract verification; real I/O (database, HTTP). Use when testing component interactions.

48 stars 10 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill integration-test-design
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/testing/skills/integration-test-design ~/.claude/skills/integration-test-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Integration Test Design

Tests that verify components work together correctly.

## Context

You are designing integration tests. These test real interactions with databases, APIs, or file systems.

## Domain Context

- **Real Dependencies**: Use real database, HTTP server, file system (or test containers)
- **Contracts**: Verify that components' assumptions about each other are correct
- **Fewer Tests**: Integration tests are slower; test key flows, not all paths
- **Setup Cost**: Creating realistic data is expensive; consider test factories
- **Flakiness Risk**: Real I/O introduces timing, concurrency issues

## Instructions

1. **Identify Interactions**: Which components must work together?
2. **Start with Real Dependencies**: Use test containers (Docker) for databases, caches
3. **Create Test Factories**: Build realistic data efficiently
4. **Test Key Flows**: Happy path + one or two error scenarios
5. **Verify Contracts**: Does the consumer of an API get what it expects?
6. **Handle Cleanup**: Reset state between tests to avoid flakiness
7. **Accept Slowness**: Slower is OK; integration tests are fewer and farther between

## Anti-Patterns

- Too many integration tests; they're slow, use resources, and should be rare
- Mocking the database in integration tests; defeats the purpose
- Shared test state; tests interfere with each other
- Ignoring cleanup; leftover data causes flaky tests
Read the full skill on GitHub

Details

Skill name
integration-test-design
Path
engineer/testing/skills/integration-test-design/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Integration Test Design skill do?

Testing multiple components together; contract verification; real I/O (database, HTTP). Use when testing component interactions.

How do I install the Integration Test Design skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Integration Test Design popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.