From configure-plugin
Checks and configures integration testing infrastructure for services, databases, and external dependencies using Supertest, pytest, or Testcontainers in JS/TS, Python, Rust, Go projects.
npx claudepluginhub laurigates/claude-plugins --plugin configure-pluginThis skill is limited to using the following tools:
Check and configure integration testing infrastructure for testing service interactions, databases, and external dependencies.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Check and configure integration testing infrastructure for testing service interactions, databases, and external dependencies.
| Use this skill when... | Use another approach when... |
|---|---|
| Setting up integration testing infrastructure with Supertest, pytest, or Testcontainers | Writing individual integration test cases for specific endpoints |
| Creating docker-compose.test.yml for local test service containers | Running existing integration tests (bun test, pytest -m integration) |
| Auditing integration test setup for completeness (fixtures, factories, CI) | Configuring unit test runners (/configure:tests instead) |
| Adding integration test jobs to GitHub Actions with service containers | Debugging a specific failing integration test |
| Separating integration tests from unit tests in project structure | Setting up API contract testing (/configure:api-tests instead) |
pwdfind . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \)find tests -maxdepth 1 -type d -name 'integration'find . -maxdepth 1 -name 'docker-compose.test.yml'find . -maxdepth 1 -name 'vitest.integration.config.*'grep -l 'supertest' package.jsonfind . -maxdepth 1 \( -name package.json -o -name pyproject.toml \) -exec grep -l 'testcontainers' {} +find . -maxdepth 1 -name '.project-standards.yaml'Parse from command arguments:
--check-only: Report compliance status without modifications (CI/CD mode)--fix: Apply fixes automatically without prompting--framework <supertest|pytest|testcontainers>: Override framework detectionIntegration Testing Stacks:
#[ignore] + testcontainers-rsKey Difference from Unit Tests:
Execute this integration testing compliance check:
Check for these indicators:
| Indicator | Component | Status |
|---|---|---|
tests/integration/ directory | Integration tests | Present |
testcontainers in dependencies | Container testing | Configured |
supertest in package.json | HTTP testing | Configured |
docker-compose.test.yml | Test services | Present |
pytest.ini with integration marker | pytest integration | Configured |
Check for complete integration testing setup:
Test Organization:
tests/integration/ directory existsJavaScript/TypeScript (Supertest):
supertest installed@testcontainers/postgresql or similar installedPython (pytest + testcontainers):
testcontainers installedhttpx or requests for HTTP testingpytest-asyncio for async testsintegration marker definedconftest.pyContainer Infrastructure:
docker-compose.test.yml existsPrint a formatted compliance report:
Integration Testing Compliance Report
======================================
Project: [name]
Language: [TypeScript | Python | Rust | Go]
Test Organization:
Integration directory tests/integration/ [EXISTS | MISSING]
Separated from unit not in src/ [CORRECT | MIXED]
Test fixtures tests/fixtures/ [EXISTS | MISSING]
Database seeds tests/seeds/ [EXISTS | N/A]
Framework Setup:
HTTP testing supertest/httpx [INSTALLED | MISSING]
Container testing testcontainers [INSTALLED | MISSING]
Async support pytest-asyncio [INSTALLED | N/A]
Infrastructure:
docker-compose.test.yml test services [EXISTS | MISSING]
Test database PostgreSQL/SQLite [CONFIGURED | MISSING]
Service isolation network config [CONFIGURED | MISSING]
CI/CD Integration:
Integration test job GitHub Actions [CONFIGURED | MISSING]
Service containers workflow services [CONFIGURED | MISSING]
Overall: [X issues found]
Recommendations:
- Install testcontainers for database testing
- Create docker-compose.test.yml for local testing
- Add integration test job to CI workflow
If --check-only, stop here.
Apply configuration based on detected project type. Use templates from REFERENCE.md:
tests/integration/) with setup filesCreate docker-compose.test.yml with:
Add corresponding npm/bun scripts for managing test containers. Use templates from REFERENCE.md.
Add integration test job to .github/workflows/test.yml with:
Use the CI workflow template from REFERENCE.md.
Create tests/fixtures/factories.ts (or Python equivalent) with:
Use factory templates from REFERENCE.md.
Update .project-standards.yaml:
standards_version: "2025.1"
last_configured: "[timestamp]"
components:
integration_tests: "2025.1"
integration_tests_framework: "[supertest|pytest|testcontainers]"
integration_tests_containers: true
integration_tests_ci: true
Print a summary of changes applied, scripts added, and next steps for running integration tests.
For detailed templates and code examples, see REFERENCE.md.
| Context | Command |
|---|---|
| Quick compliance check | /configure:integration-tests --check-only |
| Auto-fix all issues | /configure:integration-tests --fix |
| Run integration tests (JS) | bun test tests/integration --dots --bail=1 |
| Run integration tests (Python) | pytest -m integration -x -q |
| Start test containers | docker compose -f docker-compose.test.yml up -d |
| Check container health | `docker compose -f docker-compose.test.yml ps --format json |
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply all fixes automatically without prompting |
--framework <framework> | Override framework detection (supertest, pytest, testcontainers) |
# Check compliance and offer fixes
/configure:integration-tests
# Check only, no modifications
/configure:integration-tests --check-only
# Auto-fix all issues
/configure:integration-tests --fix
# Force specific framework
/configure:integration-tests --fix --framework pytest
/configure:tests - Unit testing configuration/configure:api-tests - API contract testing/configure:coverage - Coverage configuration/configure:all - Run all compliance checks