Expand description

A collection of different matching strategies provided out-of-the-box by wiremock.

If the set of matchers provided out-of-the-box is not enough for your specific testing needs you can implement your own thanks to the Match trait.

Furthermore, Fn closures that take an immutable Request reference as input and return a boolean as input automatically implement Match and can be used where a matcher is expected.

Check Match’s documentation for examples.

Structs

Match all incoming requests, regardless of their method, path, headers or body.

Match an incoming request if it contains the basic authentication header with the username and password as per RFC 7617.

Match an incoming request if it contains the bearer token header as per RFC 6750.

Match part of the body of a request.

Match exactly the body of a request.

Match part JSON body of a request.

Match exactly the header of a request.

Match exactly the header name of a request. It checks that the header is present but does not validate the value.

Match the value of a header using a regular expression. If the header is multi-valued, all values must satisfy the regular expression. If the header is missing, the mock will not match.

Match exactly the method of a request.

Match exactly the path of a request.

Match the path of a request against a regular expression.

Match exactly the query parameter of a request.

Only match requests that do not contain a specified query parameter.

Functions