native-build-tools icon indicating copy to clipboard operation
native-build-tools copied to clipboard

Run native tests without running tests on JVM first

Open dnestoro opened this issue 4 months ago • 3 comments

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 avatar Aug 22 '25 12:08 dnestoro