132-java-testing-integration-testing

Setting up Java integration tests with WireMock involves generating a BaseIntegrationTest class that handles dynamic port allocation and proper lifecycle management. This ensures per-test stub isolation and clean separation of test concerns for external HTTP dependencies.

Mocking HTTP clients with Mockito creates an anti-pattern that bypasses actual HTTP infrastructure. WireMock provides proper HTTP dependency stubbing with dynamic port allocation, ensuring tests remain isolated, maintainable, and capable of request verification.

Per-test stub isolation in Java integration tests requires standardized scaffolding that avoids global stub registration. By implementing proper lifecycle management, each test maintains clean separation of test concerns and prevents stub data leakage.

This WireMock integration testing approach explicitly supports framework-agnostic Java services. It automatically detects HTTP client dependencies from project imports and propagates dynamic port coordinates via System.setProperty to ensure reliable stub configuration.

WireMock for Java integration testing requires dynamic port allocation infrastructure and compilation checks to function reliably. It is specifically limited to HTTP dependency stubbing and does not address non-HTTP external service integration.