WireMock and Quarkus

Disclaimer: This solution page includes resources maintained by their authors outside the WireMock organization on GitHub. The info is provided as is without guarantees unless explicitly specified. Referenced projects and guidelines might be incompatible with the recent WireMock 3.x releases or the recent versions of the target technology or framework.

Please use with caution, and submit GitHub issues or pull requests to this page and referenced repositories if something is missing, broken or needs update.

Centralize and scale your API mocks with WireMock Cloud.

WireMock Extension for Quarkus #

There is a WireMock extension in the Quarkiverse! It allows running WireMock for Quarkus projects in the development mode. This is a very basic way of running WireMock together with Quarkus, and only a few configuration options are supported:

quarkus.wiremock.devservices.enabled=true
quarkus.wiremock.devservices.files-mapping=<path to wiremock root dir with mappings and __files folders>
quarkus.wiremock.devservices.port=8089
quarkus.wiremock.devservices.reload=true

References:

GitHub Repository

More info #

Testing a Quarkus application with WireMock and Rest Assured, by Giuseppe Scaramuzzino
Building a Resilient Microservice with Quarkus and WireMock, by Iain Porter