From f7e42bad8525235e00b7397a868c9f6c612fd7d5 Mon Sep 17 00:00:00 2001 From: SAY-droid427 Date: Fri, 2 Apr 2021 18:15:09 +0530 Subject: [PATCH 1/5] Added prep work for quarkus_openshift tests --- external/quarkus_openshift/README.md | 31 ++++++++++++++++++++++ external/quarkus_openshift/test.properties | 13 +++++++++ 2 files changed, 44 insertions(+) create mode 100644 external/quarkus_openshift/README.md create mode 100644 external/quarkus_openshift/test.properties diff --git a/external/quarkus_openshift/README.md b/external/quarkus_openshift/README.md new file mode 100644 index 0000000000..c6551efc8f --- /dev/null +++ b/external/quarkus_openshift/README.md @@ -0,0 +1,31 @@ +# External quarkus_openshift Tests + +Third Party container tests help verify that the Adoptium binaries are good by running a variety of Java applications inside of Docker containers. AdoptOpenJDK/openjdk-tests/Issue #172 lists the applications that we have initially targeted to best exercise the AdoptOpenJDK binaries. For each application, we choose to run a selection of their functional tests. + +## Running quarkus-openshift tests locally + +To run any AQA tests locally, you follow the same pattern: + +0. Ensure your test machine is set up with [test prereqs](https://github.com/AdoptOpenJDK/openjdk-tests/blob/master/doc/Prerequisites.md). For external tests, you do need Docker installed. + +1. Download/unpack the SDK you want to your test machine + +2. `export TEST_JDK_HOME=` + +3. `git clone https://github.com/AdoptOpenJDK/openjdk-tests.git` + +4. `cd openjdk-tests` + +5. `./get.sh` + +6. `cd TKG` + +7. export required environment variables, BUILD_LIST and EXTRA_DOCKER_ARGS (`export BUILD_LIST=external/quarkus_openshift` and `export EXTRA_DOCKER_ARGS="-v $TEST_JDK_HOME:/opt/java/openjdk"` + +8. `make compile` (This fetches test material and compiles it, based on build.xml files in the test directories) + +9. `make _quarkus_openshift_test` (When you defined BUILD_LIST to point to a directory in openjdk-tests/external, then this is a testCaseName from the playlist.xml file within the directory you chose) + +When [running these from the command-line](https://github.com/AdoptOpenJDK/openjdk-tests/blob/master/doc/userGuide.md#local-testing-via-make-targets-on-the-commandline), these tests are grouped under a make target called 'external', so 'make external' would run the entire set of tests found in the openjdk-tests/external directory. This is unadvisable! Limit what you compile and run, BUILD_LIST=external/``, and TARGET=``. + +These tests run regularly and results can be found in [TRSS Third Party Application view](https://trss.adoptopenjdk.net/ThirdPartyAppVie). diff --git a/external/quarkus_openshift/test.properties b/external/quarkus_openshift/test.properties new file mode 100644 index 0000000000..57bd8ca68a --- /dev/null +++ b/external/quarkus_openshift/test.properties @@ -0,0 +1,13 @@ +github_url="https://github.com/quarkus-qe/quarkus-openshift-test-suite.git" +script="test.sh" +test_results="testResults" +tag_version="1.3.2.Final" +environment_variable="MODE=\"java\"" +debian_packages="git wget" +debianslim_packages="${debian_packages}" +ubuntu_packages="${debian_packages}" +alpine_packages="bash git wget" +centos_packages="git wget" +clefos_packages="${centos_packages}" +ubi_packages="git wget" +ubi_minimal_packages="${ubi_packages}" From 23f4e4ab3928a370ca3d3fbcf3244f668c0fe181 Mon Sep 17 00:00:00 2001 From: SAY-droid427 Date: Fri, 2 Apr 2021 19:04:22 +0530 Subject: [PATCH 2/5] Fixed typo in quarkus-openshift tests --- external/quarkus_openshift/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/external/quarkus_openshift/README.md b/external/quarkus_openshift/README.md index c6551efc8f..d03c8e8ad9 100644 --- a/external/quarkus_openshift/README.md +++ b/external/quarkus_openshift/README.md @@ -28,4 +28,4 @@ To run any AQA tests locally, you follow the same pattern: When [running these from the command-line](https://github.com/AdoptOpenJDK/openjdk-tests/blob/master/doc/userGuide.md#local-testing-via-make-targets-on-the-commandline), these tests are grouped under a make target called 'external', so 'make external' would run the entire set of tests found in the openjdk-tests/external directory. This is unadvisable! Limit what you compile and run, BUILD_LIST=external/``, and TARGET=``. -These tests run regularly and results can be found in [TRSS Third Party Application view](https://trss.adoptopenjdk.net/ThirdPartyAppVie). +These tests run regularly and results can be found in [TRSS Third Party Application view](https://trss.adoptopenjdk.net/ThirdPartyAppView). From 7c495c230ae2acf3bd341998fbabba9cf5b40c70 Mon Sep 17 00:00:00 2001 From: SAY-droid427 Date: Fri, 2 Apr 2021 21:56:37 +0530 Subject: [PATCH 3/5] Changed README.md of quarkus_openshift tests --- external/quarkus_openshift/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/external/quarkus_openshift/README.md b/external/quarkus_openshift/README.md index d03c8e8ad9..62fb8db2b0 100644 --- a/external/quarkus_openshift/README.md +++ b/external/quarkus_openshift/README.md @@ -1,6 +1,6 @@ # External quarkus_openshift Tests -Third Party container tests help verify that the Adoptium binaries are good by running a variety of Java applications inside of Docker containers. AdoptOpenJDK/openjdk-tests/Issue #172 lists the applications that we have initially targeted to best exercise the AdoptOpenJDK binaries. For each application, we choose to run a selection of their functional tests. +Third Party container tests help verify that the Adoptium binaries are good by running a variety of Java applications inside of Docker containers. AdoptOpenJDK/openjdk-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. Quarkus Openshift tests are pulled from the [quarkus-openshift-test-suite](https://github.com/quarkus-qe/quarkus-openshift-test-suite.git) repository. These tests require an Openshift cluster environment to run. ## Running quarkus-openshift tests locally From db479da6537f4f81911dfec1b8898bcbb89aa1b0 Mon Sep 17 00:00:00 2001 From: SAY-droid427 Date: Fri, 2 Apr 2021 21:58:25 +0530 Subject: [PATCH 4/5] Added hyperlinks to README --- external/quarkus_openshift/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/external/quarkus_openshift/README.md b/external/quarkus_openshift/README.md index 62fb8db2b0..38840f9596 100644 --- a/external/quarkus_openshift/README.md +++ b/external/quarkus_openshift/README.md @@ -1,6 +1,6 @@ # External quarkus_openshift Tests -Third Party container tests help verify that the Adoptium binaries are good by running a variety of Java applications inside of Docker containers. AdoptOpenJDK/openjdk-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. Quarkus Openshift tests are pulled from the [quarkus-openshift-test-suite](https://github.com/quarkus-qe/quarkus-openshift-test-suite.git) repository. These tests require an Openshift cluster environment to run. +Third Party container tests help verify that the Adoptium binaries are good by running a variety of Java applications inside of Docker containers. AdoptOpenJDK/openjdk-tests/Issue [#172](https://github.com/AdoptOpenJDK/openjdk-tests/issues/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. Quarkus Openshift tests are pulled from the [quarkus-openshift-test-suite](https://github.com/quarkus-qe/quarkus-openshift-test-suite.git) repository. These tests require an Openshift cluster environment to run. ## Running quarkus-openshift tests locally From ffa643bf0daaef9431a42084e8852bde51539659 Mon Sep 17 00:00:00 2001 From: SAY-droid427 Date: Wed, 7 Apr 2021 08:32:34 +0530 Subject: [PATCH 5/5] Completed prepwork for quarkus_openshift tests Signed-off-by: SAY-droid427 --- external/quarkus_openshift/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/external/quarkus_openshift/README.md b/external/quarkus_openshift/README.md index 38840f9596..bf2e9f08be 100644 --- a/external/quarkus_openshift/README.md +++ b/external/quarkus_openshift/README.md @@ -1,6 +1,6 @@ # External quarkus_openshift Tests -Third Party container tests help verify that the Adoptium binaries are good by running a variety of Java applications inside of Docker containers. AdoptOpenJDK/openjdk-tests/Issue [#172](https://github.com/AdoptOpenJDK/openjdk-tests/issues/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. Quarkus Openshift tests are pulled from the [quarkus-openshift-test-suite](https://github.com/quarkus-qe/quarkus-openshift-test-suite.git) repository. These tests require an Openshift cluster environment to run. +Quarkus_openshift 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. AdoptOpenJDK/openjdk-tests/Issue [#172](https://github.com/AdoptOpenJDK/openjdk-tests/issues/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. Quarkus Openshift tests are pulled from the [quarkus-openshift-test-suite](https://github.com/quarkus-qe/quarkus-openshift-test-suite.git) repository. These tests require an Openshift cluster environment to run. ## Running quarkus-openshift tests locally