Repository navigation
Update the tests to JUnit 6 - #122
Merged
Merged
Conversation
…ocode itself stays on the Java 8 toolchain
…blishing a release
…ing robots with older versions needs the JDK
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the tests from JUnit 5.14.4 to 6.1.3. JUnit 6 needs Java 17, so the tests are now compiled and run with Java 17 by default, and with Java 25 in the second CI run. The product is still built with the Java 8 toolchain, and every jar in the setup jar is still Java 8 bytecode.
The catch is that no automated tests run on Java 8 anymore. The SecurityManager path is still covered on Java 17, and the path without it on Java 25.