Skip to main content
configure-integration-tests Integration testing: Supertest, pytest, Testcontainers. Use when setting up integration tests, creating docker-compose.test.yml, or separating from unit tests.
الانتقال إلى التثبيت سوق المهارات اكتشف واستكشف مهارات الذكاء الاصطناعي التي بناها المجتمع.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
عرض تفاصيل Prompt يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-integration-testsيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
تحميل Zip جاري التحميل... المهن ذات الصلة SOC
استنادا إلى تصنيف SOC المهني
المزيد من هذا المستودع Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
created "2025-12-16T00:00:00.000Z" modified "2026-07-05T00:00:00.000Z" reviewed "2025-12-16T00:00:00.000Z" description Integration testing: Supertest, pytest, Testcontainers. Use when setting up integration tests, creating docker-compose.test.yml, or separating from unit tests. allowed-tools Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite args [--check-only] [--fix] [--framework <supertest|pytest|testcontainers>] argument-hint [--check-only] [--fix] [--framework <supertest|pytest|testcontainers>] name configure-integration-tests
/configure:integration-tests
Check and configure integration testing infrastructure for testing service interactions, databases, and external dependencies.
When to Use This Skill
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 (use api-plugin:api-testing) 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)
Context
Project root: !pwd
Package files: !find . -maxdepth 1 \( -name 'package.json' -o -name 'pyproject.toml' -o -name 'Cargo.toml' -o -name 'go.mod' \)
Integration tests dir: !find . -path '*/tests/*' -maxdepth 2 -type d -name 'integration'
Docker compose test: !find . -maxdepth 1 -name 'docker-compose.test.yml'
Vitest integration config: !find . -maxdepth 1 -name 'vitest.integration.config.*'
Supertest dep: !find . -maxdepth 1 -name 'package.json' -exec grep -l 'supertest' {} +
Testcontainers dep: !find . -maxdepth 1 \( -name package.json -o -name pyproject.toml \) -exec grep -l 'testcontainers' {} +
Project standards: !find . -maxdepth 1 -name '.project-standards.yaml'
Parameters
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 detection
Integration Testing Stacks:
JavaScript/TypeScript : Supertest + TestcontainersPython : pytest + testcontainers-python + httpxRust : cargo test with #[ignore] + testcontainers-rsGo : testing + testcontainers-go Key Difference from Unit Tests:
Integration tests interact with real databases, APIs, and services
They test component boundaries and data flow
They typically require test fixtures and cleanup
Execution Execute this integration testing compliance check:
Step 1: Detect existing integration testing infrastructure Check for these indicators:
Indicator Component Status tests/integration/ directoryIntegration tests Present testcontainers in dependenciesContainer testing Configured supertest in package.jsonHTTP testing Configured docker-compose.test.ymlTest services Present pytest.ini with integration markerpytest integration Configured
Step 2: Analyze current state Check for complete integration testing setup:
JavaScript/TypeScript (Supertest):
Python (pytest + testcontainers):
Container Infrastructure:
Step 3: Generate compliance report Print 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.
Step 4: Configure integration testing (if --fix or user confirms) Apply configuration based on detected project type. Use templates from REFERENCE.md :
Install dependencies (supertest, testcontainers, etc.)Create test directory (tests/integration/) with setup filesCreate sample tests for API endpoints and database operationsCreate Vitest integration config (JS/TS) or pytest markers (Python)Add scripts to package.json or create run commands
Step 5: Create container infrastructure Create docker-compose.test.yml with:
PostgreSQL test database (tmpfs for speed)
Redis test instance (if needed)
Network isolation
Add corresponding npm/bun scripts for managing test containers. Use templates from REFERENCE.md .
Step 6: Configure CI/CD integration Add integration test job to .github/workflows/test.yml with:
Service containers (postgres, redis)
Database migration step
Integration test execution
Artifact upload for test results
Step 7: Create test fixtures and factories Create tests/fixtures/factories.ts (or Python equivalent) with:
Data factory functions using faker
Database seeding helpers
Cleanup utilities
Step 8: Update standards tracking 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
Step 9: Print final report Print a summary of changes applied, scripts added, and next steps for running integration tests.
Agentic Optimizations Context Command Quick compliance check /configure:integration-tests --check-onlyAuto-fix all issues /configure:integration-tests --fixRun integration tests (JS) bun test tests/integration --dots --bail=1Run integration tests (Python) pytest -m integration -x -qStart test containers docker compose -f docker-compose.test.yml up -dCheck container health `docker compose -f docker-compose.test.yml ps --format json
Flags Flag Description --check-onlyReport status without offering fixes --fixApply all fixes automatically without prompting --framework <framework>Override framework detection (supertest, pytest, testcontainers)
Examples
/configure:integration-tests
/configure:integration-tests --check-only
/configure:integration-tests --fix
/configure:integration-tests --fix --framework pytest
Error Handling
No app entry point found : Ask user to specify app locationDocker not available : Warn about testcontainers requirementDatabase type unknown : Ask user to specify database typePort conflicts : Suggest alternative ports in docker-compose
See Also
/configure:tests - Unit testing configurationapi-plugin:api-testing - Writing the Supertest / httpx+pytest tests this skill scaffolds infrastructure for/configure:api-tests - API contract testing/configure:coverage - Coverage configuration/configure:all - Run all compliance checksTestcontainers documentation : https://testcontainers.com Supertest documentation : https://github.com/ladjs/supertest 