-
-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prep work for derby tests #2490
Changes from 5 commits
d245b83
3a9a78a
cfb3662
ebfa3f3
2e11502
401ae37
686be2d
5ac3baf
3fa4a26
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
## Running External tests locally | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Before this section add: External Derby TestsDerby tests are a 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 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. Derby test material is pulled from the derby repository. Then also change the heading "Running External tests locally" to be "Running Derby 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 that you want to test to your test machine | ||
1. `export TEST_JDK_HOME=</pathToWhereYouInstalledSDK>` | ||
1. `git clone https://github.com/AdoptOpenJDK/openjdk-tests.git` | ||
1. `cd openjdk-tests` | ||
1. `./get.sh` | ||
1. `cd TKG` | ||
1. export required environment variables, BUILD_LIST and EXTRA_DOCKER_ARGS (example: `export BUILD_LIST=external/jacoco` and `export EXTRA_DOCKER_ARGS="-v $TEST_JDK_HOME:/opt/java/openjdk"` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. please use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. BUILD_LIST=external/derby |
||
1. `make compile` (This fetches test material and compiles it, based on build.xml files in the test directories) | ||
1. `make _derby_test` (When you defined BUILD_LIST to point to a directory in [openjdk-tests/external](https://github.com/AdoptOpenJDK/openjdk-tests/tree/master/external), then this is a testCaseName from the playlist.xml file within the directory you chose) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please add the following as the last section: 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 openjdk-tests/external directory. This is unadvisable! Limit what you compile and run, BUILD_LIST=external/ |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
github_url="https://github.com/apache/derby.git" | ||
script="derby-test.sh" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Remove indentation for all lines that have it (so all lines are left-aligned like line 1) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Indentation please. |
||
home_path="\${WORKDIR}/derby" | ||
tag_version="trunk" | ||
ant_version="1.10.6" | ||
debian_packages="git wget tar" | ||
debianslim_packages="${debian_packages}" | ||
ubuntu_packages="${debian_packages}" | ||
alpine_packages="bash git wget tar" | ||
centos_packages="git wget tar" | ||
clefos_packages="${centos_packages}" | ||
ubi_packages="git wget tar" | ||
ubi_minimal_packages="${ubi_packages}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add another section before this:
External derby Tests
Derby 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 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 apache/derby repository.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please change the heading to:
Running External derby tests locally