Repository navigation
Quarkus native tests - #6840
Merged
Merged
Quarkus native tests#6840
Conversation
Contributor
Author
|
Native tests now work, I need to deal with a few rough edges (option.get) and build native only when it's needed (probably have 2 tasks, one quarkusApp and one quarkusNativeApp @souvlakias feel free to add those improvements (add tasks where appropriate for the optional values with appropriate messages) in quarkus you can find some hints in io.quarkus.cli.common.build.GradleRunner if you need to |
vaslabs
marked this pull request as ready for review
February 18, 2026 11:01
Contributor
Author
|
this should be ready for review |
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
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.
Part of #3549 and #6496
Summary
This completes the basic flow of building a quarkus app by supporting building the quarkus binaries (for jvm or graalvm) and running tests against either. The native tests trigger a native app build while the "normal" tests a jar build
Implementation
Other improvements
co-authored with @souvlakias