4 <meta charset="utf-8"> |
4 <meta charset="utf-8"> |
5 <meta name="generator" content="pandoc"> |
5 <meta name="generator" content="pandoc"> |
6 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> |
6 <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes"> |
7 <title>Testing OpenJDK</title> |
7 <title>Testing OpenJDK</title> |
8 <style type="text/css">code{white-space: pre;}</style> |
8 <style type="text/css">code{white-space: pre;}</style> |
9 <link rel="stylesheet" href="../../jdk/make/data/docs-resources/resources/jdk-default.css"> |
9 <link rel="stylesheet" href="../make/data/docs-resources/resources/jdk-default.css"> |
10 <!--[if lt IE 9]> |
10 <!--[if lt IE 9]> |
11 <script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script> |
11 <script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script> |
12 <![endif]--> |
12 <![endif]--> |
13 <style type="text/css">pre, code, tt { color: #1d6ae5; }</style> |
13 <style type="text/css">pre, code, tt { color: #1d6ae5; }</style> |
14 </head> |
14 </head> |
41 $ make run-test TEST=jdk_lang |
41 $ make run-test TEST=jdk_lang |
42 $ make run-test-only TEST="gtest:LogTagSet gtest:LogTagSetDescriptions" GTEST="REPEAT=-1" |
42 $ make run-test-only TEST="gtest:LogTagSet gtest:LogTagSetDescriptions" GTEST="REPEAT=-1" |
43 $ make run-test TEST="hotspot/test:hotspot_gc" JTREG="JOBS=1;TIMEOUT=8;VM_OTIONS=-XshowSettings -Xlog:gc+ref=debug" |
43 $ make run-test TEST="hotspot/test:hotspot_gc" JTREG="JOBS=1;TIMEOUT=8;VM_OTIONS=-XshowSettings -Xlog:gc+ref=debug" |
44 $ make run-test TEST="jtreg:hotspot/test:hotspot_gc hotspot/test/native_sanity/JniVersion.java" |
44 $ make run-test TEST="jtreg:hotspot/test:hotspot_gc hotspot/test/native_sanity/JniVersion.java" |
45 $ make exploded-run-test TEST=hotspot_tier1</code></pre> |
45 $ make exploded-run-test TEST=hotspot_tier1</code></pre> |
46 |
|
47 <h3 id="configuration">Configuration</h3> |
46 <h3 id="configuration">Configuration</h3> |
48 <p>To be able to run JTReg tests, <code>configure</code> needs to know where to find the JTReg test framework. If it is not picked up automatically by configure, use the <code>--with-jtreg=<path to jtreg home></code> option to point to the JTReg framework. Note that this option should point to the JTReg home, i.e. the top directory, containing <code>lib/jtreg.jar</code> etc. (An alternative is to set the <code>JT_HOME</code> environment variable to point to the JTReg home before running <code>configure</code>.)</p> |
47 <p>To be able to run JTReg tests, <code>configure</code> needs to know where to find the JTReg test framework. If it is not picked up automatically by configure, use the <code>--with-jtreg=<path to jtreg home></code> option to point to the JTReg framework. Note that this option should point to the JTReg home, i.e. the top directory, containing <code>lib/jtreg.jar</code> etc. (An alternative is to set the <code>JT_HOME</code> environment variable to point to the JTReg home before running <code>configure</code>.)</p> |
49 <h2 id="test-selection">Test selection</h2> |
48 <h2 id="test-selection">Test selection</h2> |
50 <p>All functionality is available using the run-test make target. In this use case, the test or tests to be executed is controlled using the <code>TEST</code> variable. To speed up subsequent test runs with no source code changes, run-test-only can be used instead, which do not depend on the source and test image build.</p> |
49 <p>All functionality is available using the run-test make target. In this use case, the test or tests to be executed is controlled using the <code>TEST</code> variable. To speed up subsequent test runs with no source code changes, run-test-only can be used instead, which do not depend on the source and test image build.</p> |
51 <p>For some common top-level tests, direct make targets have been generated. This includes all JTReg test groups, the hotspot gtest, and custom tests (if present). This means that <code>make run-test-tier1</code> is equivalent to <code>make run-test TEST="tier1"</code>, but the latter is more tab-completion friendly. For more complex test runs, the <code>run-test TEST="x"</code> solution needs to be used.</p> |
50 <p>For some common top-level tests, direct make targets have been generated. This includes all JTReg test groups, the hotspot gtest, and custom tests (if present). This means that <code>make run-test-tier1</code> is equivalent to <code>make run-test TEST="tier1"</code>, but the latter is more tab-completion friendly. For more complex test runs, the <code>run-test TEST="x"</code> solution needs to be used.</p> |