What problem does it solve?
Integration tests are the most neglected layer of the testing trophy, often producing flaky results due to poor service isolation, port conflicts, and missing cleanup that waste hours of developer debugging time and let real system interaction bugs slip through to production.
Core Features & Use Cases
- Parallel-safe test execution: Runs integration test suites against real databases, caches, and external services with built-in isolation strategies to avoid flaky failures.
- Failure root cause detection: Automatically identifies common integration test failure modes including shared-DB flakes, slow container startup, port conflicts, and missing teardown, with actionable fix recommendations.
- 2026 best practice compliance: Enforces modern testing standards like Testcontainers reuse for developer machines, schema-per-test isolation, and loud failures for missing infrastructure instead of silent skips.
Use case: A team running a PostgreSQL-backed API test suite can use this skill to automatically provision containers, execute tests in parallel with proper isolation, and flag flaky tests caused by missing savepoint rollback so test writers can fix fixtures instead of debugging random failures.
Quick Start
Use the integration-test-runner skill to execute your project's integration test suite against real services and receive a structured report of passes, failures, and flaky test root causes.
