integration-test
Skill5 starsChanged 5 months agoMITView on GitHub
Testing boundaries between components, databases, and external APIs
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When validating database queries, ORM layers, and transaction logic.
- Distinctive: line 12
When ensuring microservices communicate correctly.
- Distinctive: line 13
When testing against third-party API contracts.
- Distinctive: line 17
Clean State: Ensure the database or state is reset before or after each integration test to prevent cross-test pollution.
- Distinctive: line 18
Contract Testing: Consider Consumer-Driven Contracts (like Pact) when integrating with external services to catch API changes early.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Integration Test Skill
This skill governs testing the seams and connections between various components of the system.
When to use this skill
- When validating database queries, ORM layers, and transaction logic.
- When ensuring microservices communicate correctly.
- When testing against third-party API contracts.
Guidelines
- Real Infrastructure: Where possible, use real databases (via Docker/Testcontainers) instead of in-memory mocks for accurate behavior replication.
- Clean State: Ensure the database or state is reset before or after each integration test to prevent cross-test pollution.
- Contract Testing: Consider Consumer-Driven Contracts (like Pact) when integrating with external services to catch API changes early.
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- prassanna-ravishankar/repowire★ 270same name
- alexjbarnes/cockpit★ 16same name
- phatysddev/skills★ 7same name
- u7-u7/dev-skills★ 4same name
- squall-chua/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository38 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codex/AGENTS.mdAGENTS.md
- claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- fastapiSkill
- rustSkill
- backend-codeSkill
- frontend-codeSkill
- javascript-codeSkill
- java-codeSkill
- python-codeSkill
- codeSkill
- crash-analysisSkill
- memory-debugSkill
- network-debugSkill
- performance-debugSkill
- debugSkill
- argo-cdSkill
- dockerSkill
- github-actionsSkill
- gitlab-ciSkill
- jenkinsSkill
- kubernetesSkill
- devopsSkill
- terraformSkill
- nextjsSkill
- react-nativeSkill
- api-design-planSkill
- architecture-planSkill
- database-planSkill
- security-planSkill
- planSkill
- e2e-testSkill
- testSkill
- tddSkill
- unit-testSkill
- smart-contractsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.