This PR simplifies the WireMock Test API by hiding implementation details.
Instead of referencing a QuarkusTestResourceLifecycleManager directly, a user can annotate it's test class with @ConnectWireMock. This gives us a little bit more flexibility as user tests would not need to link the WireMockServerConnector (TestResourceLifecycleManager) directly.
Furthermore, I've refrained from introducing another Inject annotation. This solution is inspired by Quarkus and the possibility to inject a DevServiceContext in a test class without any annotation at all.
This PR simplifies the
WireMock
Test API by hiding implementation details.Instead of referencing a
QuarkusTestResourceLifecycleManager
directly, a user can annotate it's test class with@ConnectWireMock
. This gives us a little bit more flexibility as user tests would not need to link theWireMockServerConnector
(TestResourceLifecycleManager) directly.Furthermore, I've refrained from introducing another
Inject
annotation. This solution is inspired byQuarkus
and the possibility to inject aDevServiceContext
in a test class without any annotation at all.Reference: https://quarkus.io/guides/getting-started-testing#testing-dev-services https://github.com/quarkusio/quarkus/blob/2.5.0.Final/integration-tests/mongodb-rest-data-panache/src/test/java/io/quarkus/it/mongodb/rest/data/panache/MongoDbRestDataPanacheIT.java