| name | test-integration |
| description | Use when choosing or reviewing integration tests for API pipelines, database behavior, external dependencies, containers, serialization, middleware, or end-to-end component boundaries. |
| last-updated | "2026-06-12T00:00:00.000Z" |
| difficulty | basic |
| tokens | ~0.5K |
Integration Testing
Portable integration-test router. Load repository-profile testing rules and scoped framework testing skills first when present.
Choose the Narrowest Honest Integration
| Need | Use | Skill |
|---|
| Controllers, endpoints, auth, middleware, serialization, route bindings | API or web-application factory test | test-integration-api |
| Repositories, ORM mapping, SQL, interceptors, transactions, concurrency | Database-backed component test | test-integration-db |
| Outbound HTTP behavior | HTTP client test double at transport boundary | test-integration-api |
| Message bus, queue, cache, object storage | Real container or approved local emulator | Repository-specific skill |
Use parameterized tests when the setup and assertions are genuinely the same across rows. Request heavyweight fixtures or containers only when the test needs them.
Setup Rules
- API/E2E: start the application through the repository's approved test host and bind external dependencies through test configuration.
- DB/component: register only the services under test and apply migrations/schema setup explicitly.
- Unit tests run first; integration tests run only after unit tests pass and only when the user explicitly allows test execution.
- Do not merge structurally different behaviors merely to reduce test count.
Related
