integration-testing
/integration-testing
Test the seams between modules with real dependencies where they are cheap and containerized ones where they are not. Use when verifying that components wired together honor the contracts unit tests assume in isolation.
- Author
- Amey-Thakur ↗
- Repository
- AI-SKILLS ↗
- Licence
- MIT
- Last repository change
- 05.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Test the seams between modules with real dependencies where they are cheap and containerized ones where they are not. Use when verifying that components wired together honor the contracts unit tests assume in isolation.
Original author description
Test the seams between modules with real dependencies where they are cheap and containerized ones where they are not. Use when verifying that components wired together honor the contracts unit tests assume in isolation.
How it works
- Method
- Litmus tests
- Boundaries
SKILL.md preview
--- name: integration-testing description: Test the seams between modules with real dependencies where they are cheap and containerized ones where they are not. Use when verifying that components wired together honor the contracts unit tests assume in isolation. --- # Integration testing Unit tests prove each module works against its own assumptions. Integration tests prove those assumptions match reality at the seams: the ORM writes the column the code reads, the queue redelivers, the HTTP client parses the vendor's error shape. Mock those seams and the suite stays green while production fails at exactly the boundary nobody exercised. The craft is using real dependencies without making the suite slow or flaky. ## Method 1. **Test one seam, not the whole app.** Pick a single boundary per test: code to database, service to service, handler to queue. A test that stands up everything to check one repository method is an end-to-end test wearing the wrong label. 2. **Use the real thing when it is cheap.** An in-process SQLite or an embedded HTTP server costs milliseconds and catches real serialization bugs. Reach for these before any container when the dependency has a lightweight real mode. 3. **Containerize the heavy, version-sensitive ones.** For Postgres, Kafka, or Redis, where behavior shifts by version, run the real image with Testcontainers so the test matches production's engine rather than a stand-in that lies about locking or JSON handling. 4. **Give each test a clean slate.** Run inside a transaction rolled back at teardown, or truncate and reseed per test. Shared mutable state across integration tests is the leading source of order-dependent failures. 5. **Fake only what you cannot run.** Third-party payment and email APIs stay behind contract-tested fakes or recorded interactions such as WireMock or VCR. Everything you can stand up locally, stand up for real. 6. **Keep the suite in its own tier.** Tag integration tests so `unit` stays sub-second on every save while integration runs on push or in CI. Blending the tiers trains people to skip the slow ones, and then all of them. ## Litmus tests - Would this test have caught a migration that renamed a column the code still reads? - Does each test target one seam, so a failure names which boundary broke? - Can the suite run on a laptop with `docker` available and no shared staging database? ## Boundaries Integration tests cover component seams, not full user journeys or single functions: defer journeys to e2e-testing and isolated logic to unit-test-design. Where a team standardizes on a fixture or container harness, use it over the tools named here.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Amey-Thakur/AI-SKILLS | 90 | MIT |
| thedaviddias/front-end-checklist | 100 | MIT |
| elastic/integration-skills | 100 | Apache-2.0 |
| s-morgan-jeffries/apple-mail-fast-mcp | 100 | MIT |
| kid-sid/codex-spellbook | 100 | MIT |
| MARUCIE/openclaw-foundry | 95 | MIT |
| Tyler-R-Kendrick/agent-skills | 95 | MIT |
| OKHP3/skillz | 90 | MIT |
Database snapshot: 13.11.2026 · package version e45bcffc6243 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 92testing
Use when creating leaf types, after refactoring, during implementation, or when testing advice is needed. Automatically invoked to write tests for new types, or use as testing expert advisor. Covers the composition ladder from rung-0 unit tests to whole-system tests, with… - 92testing
Use when creating leaf types, after refactoring, during implementation, or when testing advice is needed. Automatically invoked to write tests for new types, or use as testing expert advisor. Covers the composition ladder from rung-0 unit tests to whole-system tests, with… - 100testcontainers
When the user wants to run integration tests with real dependencies using Docker containers managed by Testcontainers. Also use when the user mentions "testcontainers," "integration testing with Docker," "database integration tests," "containerized tests," or "test with real… - 100qa-unit-testing
Creates unit tests for isolated functions and modules. Use when testing utility functions or pure logic in isolation with mocked dependencies. Not for test-first React component development (use test-first-react). - 95test-integration
Test how components work together. Test database + API, auth + user service, etc. Use when testing multi-component flows or after unit tests pass. - 90quality-unit-testing
Use when the user asks about unit testing, test doubles, mocking, stubbing, test-driven development (TDD), FIRST principles, code coverage, test structure (AAA), or unit test patterns. Do NOT use for: integration testing (quality-integration-testing), E2E testing…