testing-integration

Write integration tests with test containers, test data strategies, and WireMock API mocking.

1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/iceflower/opencode-agents-and-skills --skill testing-integration-iceflower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-integration
Source: https://github.com/iceflower/opencode-agents-and-skills/tree/main/skills/testing-integration
Command: npx skills add https://github.com/iceflower/opencode-agents-and-skills --skill testing-integration-iceflower

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of writing and executing integration tests, ensuring that different components of an application work together correctly by providing clear patterns and best practices for managing dependencies, test data, and external service interactions.

Core Features & Use Cases

  • Test Container Strategy: Provides guidance on using Docker containers for dependencies like databases and message queues.
  • Test Data Management: Outlines effective methods for setting up and cleaning test data to ensure test independence.
  • Mock Server Patterns: Details how to use mock servers for simulating external API responses.
  • Use Case: When developing a new microservice that interacts with a database and an external payment gateway, use this Skill to set up integration tests that spin up a test database container, mock the payment gateway's responses, and verify the service's data persistence and external communication logic.

Quick Start

Use the testing-integration skill to write integration tests for the new user registration API endpoint.

Frequently Asked Questions about testing-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage external dependencies in integration testing?

Manage external dependencies in integration testing by using test containers to spin up Docker instances for databases and message queues. This approach isolates the test environment, ensuring reliable and reproducible multi-component system validation.

How do I mock external API responses for integration tests?

Mock external API responses for integration tests by utilizing mock servers like WireMock. This simulates various success and failure scenarios, allowing you to verify external communication logic without relying on live third-party services.

What is the best way to handle test data in integration testing?

Handle test data in integration testing by implementing effective setup and cleanup strategies. This ensures test independence and data consistency across multiple test runs, preventing cascading failures and maintaining test isolation.

Can I use test containers for microservice integration testing?

Yes, use test containers for microservice integration testing to manage dependencies like databases and message queues. This validates data persistence and external interactions by providing isolated, disposable environments tailored for multi-component systems.

Why does integration testing fail when external services are unavailable?

Integration testing fails when external services are unavailable because multi-component systems rely on live connections for data exchange. Replacing these with mock servers and test containers provides reliable testing without external service dependencies.