4 |
4 |
5 This new way of running tests is developer-centric. It assumes that you have |
5 This new way of running tests is developer-centric. It assumes that you have |
6 built a jdk locally and want to test it. Running common test targets is simple, |
6 built a jdk locally and want to test it. Running common test targets is simple, |
7 and more complex ad-hoc combination of tests is possible. The user interface is |
7 and more complex ad-hoc combination of tests is possible. The user interface is |
8 forgiving, and clearly report errors it cannot resolve. |
8 forgiving, and clearly report errors it cannot resolve. |
|
9 |
|
10 The main target "run-test" uses the jdk-image as the tested product. There is |
|
11 also an alternate target "exploded-run-test" that uses the exploded image |
|
12 instead. Not all tests will run successfully on the exploded image, but using |
|
13 this target can greatly improve rebuild times for certain workflows. |
9 |
14 |
10 Some example command-lines: |
15 Some example command-lines: |
11 |
16 |
12 $ make run-test-tier1 |
17 $ make run-test-tier1 |
13 $ make run-test-jdk_lang JTREG="JOBS=8" |
18 $ make run-test-jdk_lang JTREG="JOBS=8" |
14 $ make run-test TEST=jdk_lang |
19 $ make run-test TEST=jdk_lang |
15 $ make run-test-only TEST="gtest:LogTagSet gtest:LogTagSetDescriptions" GTEST="REPEAT=-1" |
20 $ make run-test-only TEST="gtest:LogTagSet gtest:LogTagSetDescriptions" GTEST="REPEAT=-1" |
16 $ make run-test TEST="hotspot/test:hotspot_gc" JTREG="JOBS=1;TIMEOUT=8;VM_OTIONS=-XshowSettings -Xlog:gc+ref=debug" |
21 $ make run-test TEST="hotspot/test:hotspot_gc" JTREG="JOBS=1;TIMEOUT=8;VM_OTIONS=-XshowSettings -Xlog:gc+ref=debug" |
17 $ make run-test TEST="jtreg:hotspot/test:hotspot_gc hotspot/test/native_sanity/JniVersion.java" |
22 $ make run-test TEST="jtreg:hotspot/test:hotspot_gc hotspot/test/native_sanity/JniVersion.java" |
|
23 $ make exploded-run-test TEST=hotspot_tier1 |
18 |
24 |
19 ## Test selection |
25 ## Test selection |
20 |
26 |
21 All functionality is available using the run-test make target. In this use |
27 All functionality is available using the run-test make target. In this use |
22 case, the test or tests to be executed is controlled using the `TEST` variable. |
28 case, the test or tests to be executed is controlled using the `TEST` variable. |