-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Ability to disable running ITs against the docker image #46232
Labels
Comments
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. |
So you essentially would like |
@geoand correct. |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Feb 13, 2025
…ionTest` This can be useful when the application builds a container image as it's final artifact, but would like to use `@QuarkusIntegrationTest` to test the jar or native image based on which the container was built Closes: quarkusio#46232
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
In some cases,
quarkus.container-image.build
may be true but running integration tests against a running docker container may not be feasible. In our case, for instance, some integration tests require both the application and the test code to access the same local filesystem, which is (almost) impossible to do when running the app in a container.I would like to request the ability to control whether tests should be run in a container or not, regardless if
quarkus.container-image.build
is true.From this Zulip discussion:
https://quarkusio.zulipchat.com/#narrow/channel/187030-users/topic/quarkus.2Econtainer-image.2Ebuild.20and.20integration.20tests
Implementation ideas
No response
The text was updated successfully, but these errors were encountered: