Agent skill · software engineering · jeremylongshore
running-integration-tests
Execute integration tests validating component interactions and system
Why this skill is useful
Adds specific integration testing patterns and setup procedures that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, docker-compose installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Integration Test Runner Overview Execute integration tests that validate interactions between multiple components, services, and external systems. Tests real database queries, API calls between services, message queue publishing/consuming, and file system operations without mocking the integration boundary. Prerequisites Integration test framework installed (Jest + Supertest, pytest, JUnit 5, or Go testing) External services running (database, cache, message queue) via Docker Compose or Testcontainers Database migrations applied and seed data loaded Test configuration with connection strings pointing to test instances (not production) Sufficient timeout settings (integration tests are slower than unit tests) Instructions 1. Identify integration boundaries to test: API routes with database queries (controller-to-repository flow). Service-to-service HTTP communication. Message queue producers and consumers. File upload/download with storage services. Cache read/write operations (Redis, Memcached). 2. Set up test infrastructure: Start required services using docker-compose -f docker-compose.test.yml up -d. Or use Testcontainers to programmatically start/stop containers per test suite. Run database migrations against the test database. Seed baseline data required by the test suite. 3. Write integration tests following these patterns: API integration: Send HTTP requests via Supertest and assert responses including headers, status, and body. Database integration: Execute the service method and verify database state with direct queries. Event integration: Publish a message and verify the consumer processes it correctly. Use real implementations, not mocks, at the integration boundary. 4. Manage test data isolation: Wrap each test in a database transaction and roll back after assertion. Or truncate tables in beforeEach and re-seed minimum required data. Use unique identifiers per test to avoid collisions in shared databases. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/running-integration-tests--57ee4c