You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
You added a link to a Zulip discussion, please make sure the description of the issue is comprehensive and doesn't require accessing Zulip.
This message is automatically generated by a bot.
geoand
changed the title
@QuarkusIntegrationTest: support option to run tests against deployed service
Support option for run @QuarkusIntegrationTest tests against deployed service
Nov 1, 2021
geoand
changed the title
Support option for run @QuarkusIntegrationTest tests against deployed service
Support option for running @QuarkusIntegrationTest tests against deployed service
Nov 1, 2021
Description
As of now, if we start the
@QuarkusIntegrationTest
s 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
The text was updated successfully, but these errors were encountered: