integration-test-advisor

Guide integration testing of adapter boundaries and external dependencies.

1|Updated Mar 25, 2026

Search Tags:#mocking #integration-testing #adapters #testcontainers #msw #wiremock #test-slicing

Ready to run

npx skills add https://github.com/davidarce/devrune-starter-catalog --skill integration-test-advisor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integration-test-advisor
Source: https://github.com/davidarce/devrune-starter-catalog/tree/main/skills/integration-test-advisor
Command: npx skills add https://github.com/davidarce/devrune-starter-catalog --skill integration-test-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integration tests verify adapters at their boundaries and ensure correct collaboration across components without loading the full application context.

Core Features & Use Cases

Advisor mode: Guided review flow triggered by a GUIDANCE CONTEXT FROM PLANNER and CURRENT PLAN EXCERPT.
Test slicing guidance: Promotes loading the narrowest possible slice (repositories, HTTP clients, publishers) to verify boundaries.
External service mocking patterns: References WireMock, MSW, and TestContainers to simulate dependencies.
References-driven learning: Encourages on-demand access to detailed pattern references.

Quick Start

Invoke the advisor with a plan excerpt to generate a structured integration-test review.

Frequently Asked Questions about integration-test-advisor

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

FAQPage Schema

How do I design integration test slices for backend services interacting with databases and messaging systems?▼

Test slicing loads the narrowest possible component set, such as repositories or HTTP clients, to verify adapter boundaries without loading the full application context. This approach isolates external dependencies and ensures correct collaboration across components.

What are the best patterns for mocking external HTTP services and databases in integration tests?▼

Mocking external HTTP services and databases is best handled using WireMock, MSW, and TestContainers. These tools simulate external dependencies to enforce deterministic, safe tests and validate adapter interactions at service boundaries.

When do I need integration testing for adapter boundaries instead of loading the full application context?▼

Integration testing for adapter boundaries is needed when verifying interactions with databases, HTTP services, and messaging systems without the overhead of the full application context. It ensures correct collaboration while keeping tests deterministic and safe.

How do I generate a structured integration test review for my current development plan?▼

To generate an integration test review, invoke the advisor with a plan excerpt and guidance context. It triggers an advisor-mode workflow that provides structured reviews and reference-pattern guidance for your specific testing requirements.

Does this advisor support guided workflows for validating HTTP client and publisher interactions?▼

Yes, it supports guided workflows for validating HTTP client and publisher interactions. It enforces advisor-mode workflows and applies reference patterns like WireMock and MSW to ensure deterministic and safe adapter tests.

Why should I use TestContainers for integration testing instead of standard mocking frameworks?▼

TestContainers simulates external dependencies like databases and messaging systems within integration tests, validating adapter interactions safely. Unlike standard mocking, it provides reference-pattern guidance for deterministic tests without loading the full application context.