testing-integration
Run integration tests for component interactions
Works with
--- name: testing-integration description: Run integration tests for component interactions license: MIT --- # Integration Testing Test interactions between multiple components, modules, or services. ## When to use me Use this skill when: - Components have been unit tested and need to work together - Testing API contracts between services - Verifying database interactions work correctly - Checking third-party service integrations - Ensuring microservices communicate properly - Validating data flows through the system ## What I do - Identify integration points between components - Set up test environments with real or test databases - Configure service connections and API endpoints - Test data flow between integrated components - Verify error handling across component boundaries - Check contract compliance between services - Validate end-to-end workflows without UI ## Examples ```bash # Run integration tests npm run test:integration # Node.js integration tests pytest tests/integration/ # Python integration tests go test -tags=integration # Go integration tests # Test specific integrations npm run test:integration -- --grep "database" pytest tests/integration/test_api_client.py # Run with test containers for external services docker-compose -f docker-compose.test.yml up --abort-on-container-exit ``` ## Output format ``` Integration Test Results: ────────────────────────────── ✅ API Service ↔ Database ✓ User data persists correctly ✓ Transaction rollback on failure ❌ Payment Service ↔ Banking API ✗ Authentication token refresh fails ✗ Currency conversion rate mismatch ⚠️ Email Service ↔ Queue ⚠️ Message retention period too short Summary: 8 passed, 2 failed, 1 warning ``` ## Notes - Integration tests are slower than unit tests - Use test databases or in-memory databases - Mock only external third-party services - Test happy paths and error scenarios - Clean up test data between tests - Consider using test containers for external dependencies - Focus on contract testing for microservices
More Testing skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
setup-pre-commit
mattpocock/skills
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

