Scala tests are part of the external third-party application tests that help verify that the Adoptium binaries are good by running a variety of Java applications inside of Docker containers. Adoptium/aqa-tests/Issue #172 lists the applications that we have initially targeted to best exercise the Adoptium binaries. For each application, we choose to run a selection of their functional tests. Scala tests are pulled from the scala-test-suite repository.
To run any AQA tests locally, you follow the same pattern:
-
Ensure your test machine is set up with test prereqs. For external tests, you do need Docker installed.
-
Download/unpack the SDK you want to your test machine
-
export TEST_JDK_HOME=</pathToWhereYouInstalledSDK> -
git clone https://github.com/adoptium/aqa-tests.git -
cd aqa-tests -
./get.sh -
cd TKG -
export required environment variables, BUILD_LIST and EXTRA_DOCKER_ARGS (
export BUILD_LIST=external/scalaandexport EXTRA_DOCKER_ARGS="-v $TEST_JDK_HOME:/opt/java/openjdk" -
make compile(This fetches test material and compiles it, based on build.xml files in the test directories) -
make scala_test(When you defined BUILD_LIST to point to a directory in aqa-tests/external, then this is a testCaseName from the playlist.xml file within the directory you chose)
When running these from the command-line, these tests are grouped under a make target called 'external', so 'make external' would run the entire set of tests found in the aqa-tests/external directory. This is unadvisable! Limit what you compile and run, BUILD_LIST=external/<someSubDirectory>, and TARGET=<testCaseNameFromSubdirPlaylist>.
These tests run regularly and results can be found in TRSS Third Party Application view.