Using Quarkus and WireMock when running tests.
- Quarkus 2.2.3.Final with Java 17
- Dynamic port allocation for WireMock (see WireMockEnabled)
- Configuring REST Client automatically (see CountryServiceRestClientTest)
- WireMockServer injectable in tests (see CountryServiceHttpClientTest)
- Works when running tests
- Works in continuous-test-mode / dev-mode
If you want to learn more about Quarkus, please visit its website: https://quarkus.io/ .
You can run your application in dev mode that enables live coding using:
./mvnw compile quarkus:devNOTE: Quarkus now ships with a Dev UI, which is available in dev mode only at http://localhost:8080/q/dev/.
The application can be packaged using:
./mvnw packageIt produces the quarkus-run.jar file in the target/quarkus-app/ directory.
Be aware that it’s not an über-jar as the dependencies are copied into the target/quarkus-app/lib/ directory.
If you want to build an über-jar, execute the following command:
./mvnw package -Dquarkus.package.type=uber-jarThe application is now runnable using java -jar target/quarkus-app/quarkus-run.jar.
You can create a native executable using:
./mvnw package -PnativeOr, if you don't have GraalVM installed, you can run the native executable build in a container using:
./mvnw package -Pnative -Dquarkus.native.container-build=trueYou can then execute your native executable with: ./target/quarkus-with-wiremock-1.0.0-SNAPSHOT-runner
If you want to learn more about building native executables, please consult https://quarkus.io/guides/maven-tooling.html.