integration-testing
Designs comprehensive integration testing strategies including API testing, database testing, microservices testing, end-to-end testing, and test automation frameworks. Produces test plans, test cases, test data strategies, and CI/CD integration. Use when designing test strategies, writing integration tests, setting up test automation, testing APIs, testing microservices, or when users mention integration testing, API testing, E2E testing, test automation, or quality assurance.
Works with
--- name: integration-testing description: Designs comprehensive integration testing strategies including API testing, database testing, microservices testing, end-to-end testing, and test automation frameworks. Produces test plans, test cases, test data strategies, and CI/CD integration. Use when designing test strategies, writing integration tests, setting up test automation, testing APIs, testing microservices, or when users mention integration testing, API testing, E2E testing, test automation, or quality assurance. license: MIT --- # Integration Testing ## Overview Designs comprehensive integration testing strategies including API testing, database testing, microservices testing, end-to-end testing, and test automation frameworks ## Core Capabilities 1. **Core Capability 1** - Description 2. **Core Capability 2** - Description 3. **Core Capability 3** - Description ## Quick Start **Basic Workflow:** 1. Analyze requirements and context 2. Apply appropriate patterns 3. Validate and test results 4. Document findings and recommendations ## Detailed Topics Load reference files based on specific needs: - **Activation Guidelines**: See [activation-guidelines.md](references/activation-guidelines.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance - **Cicd Integration**: See [cicd-integration.md](references/cicd-integration.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance - **Core Capabilities**: See [core-capabilities.md](references/core-capabilities.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance - **Integration Testing Process**: See [integration-testing-process.md](references/integration-testing-process.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance - **Test Coverage And Reporting**: See [test-coverage-and-reporting.md](references/test-coverage-and-reporting.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance - **Test Patterns**: See [test-patterns.md](references/test-patterns.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance - **Testing Best Practices**: See [testing-best-practices.md](references/testing-best-practices.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance - **Testing Frameworks**: See [testing-frameworks.md](references/testing-frameworks.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance - **Testing Frameworks And Tools**: See [testing-frameworks-and-tools.md](references/testing-frameworks-and-tools.md) when: - Working with related functionality - Need specific patterns or examples - Require detailed guidance
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.

