Quarkus

Test Quarkus applications against Mokksy or AI-Mocks by replacing outbound HTTP and AI provider dependencies with deterministic local endpoints.

Quarkus follows the same base-URL replacement pattern as Spring Boot: start Mokksy before the test, configure the application to call mokksy.baseUrl(), then exercise the real Quarkus HTTP client code.

In practice, that usually means overriding the Quarkus config value that normally holds the external service base URL during test startup, rather than swapping clients manually inside the application.

1Quarkus test -> application HTTP client -> Mokksy -> stubbed external API

Use this for standard HTTP integrations as well as AI provider clients that sit behind Quarkus services.

Demos

Where to go next

This is a routing guide for Quarkus projects. Use the linked Mokksy and AI-Mocks pages for the tested APIs, and override the outbound base-URL configuration value in your Quarkus test setup.