-
Notifications
You must be signed in to change notification settings - Fork 354
Support running JUnit 5 tests as native image #22
Comments
Current work on the POC can be seen in the following feature branch: https://github.com/sbrannen/spring-framework/commits/graalvm-testing Status Quo: For At the moment we are often excluding entire test classes if a single contained test method cannot execute within a native image. Later iterations will improve on this to increase test coverage. Work will continue solely with |
Note that Log4J will eventually provide out-of-the-box GraalVM native image configuration. Consult the Generate reflect-config.json for GraalVM during annotation processing issue for details. See also: oracle/graal#808 |
UpdateCurrent work can be viewed here: spring-projects/spring-framework@master...sbrannen:graalvm-testing For The list of tests to execute within the native image is no longer hand crafted. Instead, the new In addition, we no longer need to manually download the |
The |
UpdateAs of the latest changes in the feature branch, unit testing within the ExampleExecuting the following within the ../gradlew --offline --no-build-cache -DnativeImageTesting=true clean testInNativeImage Results in output similar to the following:
|
With the latest commits to the feature branch, tests in
That equates to 1025 out of 1484 tests (i.e., 69%). |
This has been fixed in https://github.com/palantir/gradle-graal/releases/tag/0.6.1 |
@aclement has recently demonstrated it is possible to run a subset of Spring Framework unit tests as native images. The purpose of this issue is to start from that POC to experiment and identify the next steps toward a more robust and mature arrangement that would allow to run a subset of Spring Framework and Spring Boot JUnit 5 tests as a native image in order to:
Goal of this issue:
ExecutionCondition
).spring-graal-native
for now)java
andnative-image
currently in the path, or in a container)Non-goal of this issue:
The text was updated successfully, but these errors were encountered: