-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run JUnit tests with GraalVM #6296
Comments
Interesting... |
Wow
|
I want to confirm all of OkHttp works with Graalvm, and I'm hoping to demonstrate that by getting the entire test suite running inside Graalvm. #6296
I want to confirm all of OkHttp works with Graalvm, and I'm hoping to demonstrate that by getting the entire test suite running inside Graalvm. #6296
Do you want any help with any aspect of this? exploring best ways to setup reflection with junit? adding support in PlatformRule to use NativeImageDetector.inNativeImage()? fixing tests? I'll assume no, but happy to chip in when and if you think I can help. |
Yeah I'd love help. In hacking on this yesterday I learned just how annoying it is to pull one module’s tests into another module's dependencies. My conclusion was to make this into a task we can use from any module, and not a separate module. Which led to this PR: The next natural step I see while waiting on the above is to temporarily manually move a few tests into native-image-tests/src/main/java to execute 'em in Graal. Presumably there's gonna be challenges there! Getting CallTest passing will be a nice milestone. |
@swankjesse +1 - graal itself doesn't add additional modules, just a target for running nativeImage. Is that an option here? nativeImage -> jar |
Yep! |
POC graal test with okhttp and mockwebserver with only Junit5
|
Closing this out, I think remaining work is really a migrate all tests to junit5 task. |
It's quite possible there's gaps on OkHttp when executed on GraalVM.
We should do the Gradle work to run our test suite on it. It appears possible, though awkward.
spring-attic/spring-native#22
Spring uses JUnit 5 in the above example. If doing our tests on GraalVM requires upgrading to JUnit 5, we should probably do that too.
The text was updated successfully, but these errors were encountered: