Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support option for running @QuarkusIntegrationTest tests against deployed service #445

Closed
snowdrop-bot opened this issue Nov 1, 2021 · 0 comments
Assignees
Labels
7 - Community development upstream/closed The issue has been closed in the upstream repository

Comments

@snowdrop-bot
Copy link
Collaborator

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


quarkusio#21131


$upstream:21131$

@snowdrop-bot snowdrop-bot added the upstream/closed The issue has been closed in the upstream repository label Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
7 - Community development upstream/closed The issue has been closed in the upstream repository
Projects
None yet
Development

No branches or pull requests

2 participants