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
As a Galasa user, I want the Galasa Managers to be tested in the integration test suite against Java 17, so that I know the Manager code works reliably with that Java version.
Background
Tests for Java 17 haven't been added into the test suite since we added Java 17 support.
Story
Add v17 to enum JavaVersion in the Java Manager
Obtain a Java 17 archive and add it to the Java Archive download site (site that we stand up ourselves)
Add CPS property that points the Java Manager to that archive link for v17
Add a new test class for each existing test that tests Java 17 instead of 11 (so duplicate each class thats something like CoreLocalJava11Ubuntu, and make CoreLocalJava17Ubuntu)
Point these test classes at Java 17 in the JavaUbuntuInstallation annotation (see example)
The text was updated successfully, but these errors were encountered:
Story
As a Galasa user, I want the Galasa Managers to be tested in the integration test suite against Java 17, so that I know the Manager code works reliably with that Java version.
Background
Tests for Java 17 haven't been added into the test suite since we added Java 17 support.
Story
JavaVersion
in the Java ManagerThe text was updated successfully, but these errors were encountered: