Skip to content

Conversation

dnestoro
Copy link
Collaborator

@dnestoro dnestoro commented Aug 22, 2025

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.

@dnestoro dnestoro self-assigned this Aug 22, 2025
@oracle-contributor-agreement oracle-contributor-agreement bot added the OCA Verified All contributors have signed the Oracle Contributor Agreement. label Aug 22, 2025
@dnestoro dnestoro changed the title Run native tests without running tests on JVM before Run native tests without running tests on JVM first Aug 22, 2025
@dnestoro dnestoro force-pushed the dnestoro/run-native-tests-without-previous-jvm-run branch from 8dfa083 to 05b4dbd Compare August 28, 2025 13:24
@dnestoro dnestoro force-pushed the dnestoro/run-native-tests-without-previous-jvm-run branch from 05b4dbd to 23494be Compare August 28, 2025 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCA Verified All contributors have signed the Oracle Contributor Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The native JUnit tests cannot be executed without the prior run of JVM tests
2 participants