132-java-testing-integration-testing

To set up Java integration tests with WireMock, you need a Maven project with WireMock dependencies and a resources layout. The skill analyzes your codebase, detects HTTP client usage, and generates a BaseIntegrationTest scaffold with dynamic coordinates.

Testing outbound HTTP dependencies in a Java service is best achieved by using WireMock to stub HTTP calls. This approach creates a REST-testing topology that verifies HTTP interactions while keeping tests isolated and deterministic.

Yes, this approach supports detecting multiple HTTP clients including HttpClient, RestTemplate, Feign, Retrofit, and OkHttp. It analyzes your codebase to identify these outbound HTTP dependencies and proposes a tailored REST-testing topology based on WireMock.

You should avoid global stubs and mocked HTTP clients because they are anti-patterns that compromise test isolation. Using WireMock as an HTTP stub preserves real HTTP-pipeline testing, ensuring your tests remain deterministic and accurately reflect integration points.

To propagate dynamic coordinates to your Java integration tests, the generated BaseIntegrationTest includes a @BeforeAll block that sets these coordinates via System.setProperty(). This ensures the WireMockExtension and @RegisterExtension have the necessary configuration.