As of now, if we start the @QuarkusIntegrationTests through maven, the artifact is started and test are executed against this artifact. This might be problematic in situations where we need other dependent services, e.g. a database, messaging system,... and cannot use DinD (and, in return, Testcontainers).
Implementation ideas
A possible solution to this problem would be to first deploy the artefact (e.g. in a k8s/openshift cluster) and then execute the tests so that they run against the deployed resources (e.g. by specifying a root URL to access the deployment).
Description
As of now, if we start the
@QuarkusIntegrationTests through maven, the artifact is started and test are executed against this artifact. This might be problematic in situations where we need other dependent services, e.g. a database, messaging system,... and cannot use DinD (and, in return, Testcontainers).Implementation ideas
A possible solution to this problem would be to first deploy the artefact (e.g. in a k8s/openshift cluster) and then execute the tests so that they run against the deployed resources (e.g. by specifying a root URL to access the deployment).
FTR: https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/Point.20.40QuarkusIntegrationTest.20to.20already.20running.20instance
https://github.com/quarkusio/quarkus/issues/21131
$upstream:21131$