Skip to content

SYSTEM Cited by 1 source

WireMock

WireMock (wiremock.org) is an HTTP mock server, Java-first, with an embedded mode (start inside a JUnit test JVM) and a standalone mode (run as a Docker container). Canonical companion for Testcontainers-based integration tests that need to stand in for an external HTTP peer.

Shape: declare stubs (request matchers → responses). Supports recording real traffic and replaying it, request templating, response delays, fault injection (random resets / truncated responses), and JSON-schema validation on the request side.

Used heavily in the Java / Spring Cloud ecosystem — Spring Cloud Contract generates WireMock stubs as one of its output formats so that providers' contracts ship as deployable mock artefacts.

Relevance to Testcontainers ingest

Zalando ZMS names WireMock (alongside systems/mockserver) as an HTTP-peer-mocking option inside Testcontainers-based ITs. Same pattern: container runs, system-under-test points at the dynamic port via @DynamicPropertySource, stubs declared per test or per base class.

Same caveat as MockServer: a stubbed IT does not catch real-API drift. Zalando recommends pairing with concepts/contract-testing (Spring Cloud Contract, which itself can emit WireMock stubs for consumer-side verification).

Seen in

Last updated · 476 distilled / 1,218 read