Expand description
A WireMock server container for stubbing HTTP dependencies in integration tests.
§Readiness — verified against a real 3.13.2 boot
WireMock 3.x ships a dedicated /__admin/health endpoint (unlike some older 2.x
builds, where /__admin/mappings was the only reliable 200). Verified directly
against a real container:
$ curl http://127.0.0.1:<port>/__admin/health
{"status":"healthy","message":"Wiremock is ok","version":"3.13.2","uptimeInSeconds":9,...}so this module waits on that endpoint rather than falling back to
/__admin/mappings.
No control characters were found in the image’s baked env (checked via
docker image inspect), and no with_memory_limit override was
needed — the JVM boots comfortably on msb’s default ~450M microVM RAM (observed
~5.5s IT round-trip on msb; a small embedded-Jetty app, not a JVM-heavy cluster
like Pinot — no memory-ladder escalation was needed).
This is the Rust ecosystem’s missing piece too: there is no first-class in-process WireMock story for Rust integration tests, so this module fills a real gap.
Structs§
- Wire
Mock Container - A WireMock stub-server container.
- Wire
Mock Guard - The running guard for a
WireMockContainer.