integration-test-advisor

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.

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.

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.

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.

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.

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.