Document current behaviour for integration tests #48725
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gsmet
reviewed
Jul 2, 2025
Comment on lines
+558
to
+559
| Why the different behaviour? Quarkus builds are _long_, and running every integration test twice would make them even longer. | ||
| In most cases, coverage in the native build is sufficient. |
There was a problem hiding this comment.
It looks like we are only testing things in native, which is not exactly true as there is a Surefire counterpart. I wonder if we could avoid the confusion?
There was a problem hiding this comment.
Should we say something like "covering integration tests in the native build is sufficient"?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.