Integration Testing

Organization

DevelopersGlobal

integration-testing

Test real system boundaries, not mocks of mocks. Integration tests verify that components work together, not that they work in isolation.

Overview

Publisher	DevelopersGlobal
Repository	`ai-agent-skills`
Skill name	`integration-testing`
Stars	212
Forks	33
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by DevelopersGlobal on GitHub. Read the source before you install it.

Installation

Install the Integration Testing AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/integration-testing
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/integration-testing

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/DevelopersGlobal/ai-agent-skills.git /tmp/ai-agent-skills
mkdir -p .claude/skills
cp -r /tmp/ai-agent-skills/skills/integration-testing .claude/skills/integration-testing

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Integration Testing in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Integration Testing on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Integration Testing is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Overview

Unit tests verify components work in isolation. Integration tests verify they work together. The gap between these two is where most production bugs hide. This skill ensures integration tests cover the real system boundaries.

When to Use

After unit tests are passing
Before any feature ships to production
When testing database, API, or third-party service interactions

Process

Step 1: Identify Real Boundaries

Map every boundary in the system: code ↔ database, code ↔ external API, service ↔ service, frontend ↔ backend.
Rank boundaries by failure impact.
Integration tests should cover the top 5 highest-impact boundaries.

Verify: Boundary map created. Top 5 prioritized.

Step 2: Test Real, Not Mocked

Use a real test database (not SQLite in-memory if prod uses PostgreSQL).
Use contract tests for external APIs — test against a recorded real response.
Use test containers for services that would otherwise require mocking.
Mock only: third-party services you can't control, slow services with contract tests already in place.

Verify: No internal boundaries are mocked in integration tests.

Step 3: Test the Happy Path AND Failure Cases

Happy path: the system works end-to-end for the primary use case.
Failure cases: database down, API returns 500, timeout, malformed response.
State verification: after each action, verify the state in the real database.

Verify: At least 1 failure case per boundary is tested.

Step 4: Keep Tests Independent

Each test cleans up its own state (transactions rolled back, test data deleted).
Tests don't share state with each other.
Tests can run in any order.

Verify: Test suite passes when run in random order.

Common Rationalizations (and Rebuttals)

Excuse	Rebuttal
"Unit tests are enough"	Unit tests with mocks test that your mocks work, not your system.
"Integration tests are slow"	Slow tests are better than discovering bugs in production. Optimize the setup, not the coverage.
"We test in staging"	Staging is not a substitute for automated tests. It's too slow and too manual.

Verification

Real boundaries identified and prioritized
Integration tests use real dependencies (not mocks of internal components)
Happy path and failure cases tested for each boundary
Tests are independent (can run in any order)
Test cleanup is reliable

Frequently asked questions

What does the Integration Testing AI skill do?

Test real system boundaries, not mocks of mocks. Integration tests verify that components work together, not that they work in isolation.

Why use Integration Testing on TypingMind?

Because you install it once and use it with any model. Integration Testing is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Integration Testing in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/DevelopersGlobal/ai-agent-skills/tree/main/skills/integration-testing. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Integration Testing?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Integration Testing?

As many as you like. As long as a model supports skills, you can use Integration Testing with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Integration Testing AI skill free?

Yes. It is published on GitHub by DevelopersGlobal under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Auteur

NousResearch

OrganizationPopular

Design and build cinematic, award-level web pages.

Skill Creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a…

E2e Cucumber Playwright

langgenius

OrganizationPopular

Use when writing, changing, or reviewing Cucumber and Playwright tests under `e2e/`, including feature files, step definitions, support code, scenario tags, locators, and assertions. Do not use for…

Channel Message Flows

openclaw

OrganizationPopular

Use when running QA Lab channel message flow evidence.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Overview

When to Use

Process

Step 1: Identify Real Boundaries

Step 2: Test Real, Not Mocked

Step 3: Test the Happy Path AND Failure Cases

Step 4: Keep Tests Independent

Common Rationalizations (and Rebuttals)

Verification

References

Frequently asked questions

Related AI Skills

Set up your own AI workspace now