Run native tests without running tests on JVM first #765
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.
Problem: At the moment, every time we run native tests (with both Maven or Gradle), we must run tests on JVM first, in order to collect
test-ids
required for native run. With more complex tests, this additional step increases time required for tests execution.Idea: We should use JUnit's dry-run mode to just collect
test-ids
without executing tests on JVM.Solution: we can set
junit.platform.execution.dryRun.enabled
system property to true when executing tests on JVM (maven change, gradle change).NOTE: Since this approach changes the default behavior, we should bump major version for the next release.