You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all of the smoke tests run the tests on the JVM against an app running as a separate process (on the JVM using java -jar or as a native image). We should add something that exercises nativeTest with various things (slices, @SpringBootTest with a mock environment, @SpringBootTest with a web server, etc).
The text was updated successfully, but these errors were encountered:
I pushed a change which executes the unit tests on the JVM and in a native image. The nativeAotTests task now depends on nativeTest. I removed the useless unit tests from most of the smoke tests.
The native unit tests can be seen for example in the command-line-runner smoke test.
I'd like to revisit this as I think it's resulted in individual smoke tests covering too many things. It feels like we might need two separate kinds of smoke test:
An app smoke test that runs an AOT-processed app on the JVM or in a native image and tests it
A test smoke test that runs AOT-processed tests on the JVM or in a native image
This separation will mean that we have four different tasks that can be run to test different things:
app smoke test
a. test the app on the JVM
b test the app in a native image
test smoke test
a. Run the AOT-processed tests on the JVM
b. Run the AOT-processed tests in a native image
These should be configured as separate tasks on CI so that the results provide as clear a picture as possible of what does and does not work.
Uh oh!
There was an error while loading. Please reload this page.
Currently, all of the smoke tests run the tests on the JVM against an app running as a separate process (on the JVM using
java -jar
or as a native image). We should add something that exercisesnativeTest
with various things (slices,@SpringBootTest
with a mock environment,@SpringBootTest
with a web server, etc).The text was updated successfully, but these errors were encountered: