Stand-In Definitions

WireMock renders a stub body only when the response-template transformer is attached to that response. Without it, WireMock treats the body as literal bytes and returns the Handlebars source unchanged. Attach it with withTransformers, or launch WireMock with --global-response-templating.

Put both WireMock stubs into one scenario with inScenario. The first requires the start state and calls willSetStateTo to move the conversation on. The second requires that new state and answers only once the first has served.

Negate the header name. MockServer holds request names and values as NottableString values, so a header built from not("X-Sweep-Tenant") matches only calls that carry no such header. Negating the value instead matches a header that is present but different.

Yes. MockServer matches on a subset, not on equality. Every header, cookie and query-string parameter you name is a constraint the request must satisfy; every one you do not name is ignored, however many the client sends.

It serves raw bytes. WireMock's withBase64Body takes a base64-encoded string and decodes it into the exact body bytes, so a binary payload such as a signed watering permit survives, while withBody takes text that must go through a character encoding.

Because WireMock sorts matching stubs by priority ascending and serves the first one, so the number is a place in a queue rather than a strength. Raising it moves the stub further back, behind the default five.

Attach WireMock's response-template transformer, then reference the request model from the body. WireMock exposes the call as request, so request.path, request.query and request.body are readable, and the jsonPath helper pulls a single field out of a JSON payload.

Move it once the payload buries the matcher, when several mappings need the same fixture, or when the bytes want to be a real file. WireMock's withBodyFile names a file under __files, leaving the mapping with the matcher and status.

Almost always the stub set a body and no media type. In WireMock the reply carries only the headers the response definition declares, so a client that checks Content-Type before decoding rejects a perfectly correct body. Add withHeader explicitly.

Nothing about your stub changed. The new mapping also matches those requests and sorts ahead of yours, either by carrying a lower atPriority number or by arriving later at equal priority. Your stub still matches; it is no longer first.

In WireMock, any() is a request-pattern builder that accepts every HTTP method while still applying the URL matcher you give it. WireMock's anyUrl() is a URL matcher that accepts every URL. Together they widen two separate axes.

It adds a predicate to the expectation's request side. The call matches only if the URL query string carries a borough parameter whose value matches camden. A request without that parameter is simply not matched by this expectation.

In WireMock, aResponse() starts the response builder, withStatus sets the numeric HTTP status, and withBody sets the literal reply body as text. WireMock adds response headers separately, through withHeader. Nothing in the reply is inferred from the request.

WireMock's atPriority sets a stub's precedence number. A stub that never calls it sits at DEFAULT_PRIORITY, which is five. Lower numbers win, so among several matching stubs WireMock serves the lowest-numbered one, whatever order they were registered in.

WireMock's randomValue helper generates a value such as a UUID, and its now helper renders the current time, with optional offset and format. Both need the response-template transformer attached, or WireMock serves the raw helper text itself as the body.

WireMock's urlEqualTo matches the whole request URL, path and query string together. WireMock's urlPathEqualTo matches the path alone and ignores everything after the question mark. Add a query parameter and the urlEqualTo stub stops matching, while urlPathEqualTo still fires.

Every WireMock scenario begins in the state named Started. Scenario.STARTED is a String constant holding exactly that text, not an enum value, so the comparison is literal. A stub waiting on STARTED in capitals therefore never fires.

At equal priority WireMock serves the stub registered most recently, because it sorts matching stubs by priority ascending and then by insertion index descending. Newest-wins is only the tie-break. A later stub with a weaker priority number still loses.

In WireMock the method is chosen by the request-pattern builder itself — get, post, put, delete, patch or any — each taking a URL matcher. WireMock's withMethod belongs to its webhook and logged-request builders, not to stub matching at all.

In WireMock, ignoreExtraElements and ignoreArrayOrder forgive only additions and array order. A missing field, a changed value or a different JSON type still makes WireMock's equalToJson miss, and so does a body that is not valid JSON at all.

In WireMock, matchingJsonPath selects part of a body with a JSONPath expression and matches when the expression returns something. The rest of the payload may vary freely. Use it when one field decides which canned response the stub returns.

A WireMock scenario name identifies one shared state machine. Every stub naming it reads and writes the same state, so two unrelated dive-log conversations advance each other. A stub waiting on a state the other side consumed then never serves.

MockServer compares a header value literally first, then retries it as a regular expression. The dot in acme.co is therefore a wildcard that any character satisfies, so acmeXco matches as well. Escape the metacharacter to pin the value.

Turn on WireMock's --global-response-templating when every mapping on that instance is dynamic and repeating the transformer name is pure noise. Keep per-stub templating for a mixed set, because global rendering parses every body, including ones that legitimately contain braces.

Handlebars escapes double-brace output for HTML, so WireMock turns a quote into the " entity. In WireMock, the triple-brace form emits the helper's output raw instead. Use it whenever a WireMock template injects JSON or XML into a reply.

Default to WireMock's equalToJson with ignoreExtraElements on, so stubs survive additive payload changes, and use matchingJsonPath for the one or two fields that actually select the response. Reserve strict whole-body equality for the few endpoints whose entire payload genuinely matters.

Reserve narrow bands around WireMock's default of five: a low band for deliberate overrides, the untouched default for ordinary stubs, and a high band for fallbacks. Require every explicit atPriority number to name the mapping it outranks.

Mountebank cycles a stub's responses array: each matching request takes the next entry, and the sequence wraps at the end. The repeat field on a response holds that entry for several calls. repeat is a response field, not a behavior.

In WireMock, equalToXml compares the whole request document, so any element the client adds breaks the stub. WireMock's matchingXPath selects one node instead and matches when it exists. Use XPath when only part of the XML decides the response.