OpenJDK / amber / amber
changeset 55525:0cf2c87ce79a
8221357: Update test documentation by deleting "cd test && make"
Reviewed-by: dholmes, tbell, erikj
Contributed-by: Jing Tian <jingtian@loongson.cn>
| author | dholmes |
|---|---|
| date | Mon, 25 Mar 2019 17:29:43 -0400 |
| parents | 75445a7c2c04 |
| children | 418fbdb1b581 |
| files | doc/testing.html doc/testing.md |
| diffstat | 2 files changed, 3 insertions(+), 4 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/testing.html Mon Mar 25 20:57:07 2019 +0100 +++ b/doc/testing.html Mon Mar 25 17:29:43 2019 -0400 @@ -39,7 +39,7 @@ <h2 id="using-make-test-the-run-test-framework">Using "make test" (the run-test framework)</h2> <p>This new way of running tests is developer-centric. It assumes that you have built a JDK locally and want to test it. Running common test targets is simple, and more complex ad-hoc combination of tests is possible. The user interface is forgiving, and clearly report errors it cannot resolve.</p> <p>The main target <code>test</code> uses the jdk-image as the tested product. There is also an alternate target <code>exploded-test</code> that uses the exploded image instead. Not all tests will run successfully on the exploded image, but using this target can greatly improve rebuild times for certain workflows.</p> -<p>Previously, <code>make test</code> was used invoke an old system for running test, and <code>make run-test</code> was used for the new test framework. For backward compatibility with scripts and muscle memory, <code>run-test</code> (and variants like <code>exploded-run-test</code> or <code>run-test-tier1</code>) are kept as aliases. The old system can still be accessed for some time using <code>cd test && make</code>.</p> +<p>Previously, <code>make test</code> was used to invoke an old system for running tests, and <code>make run-test</code> was used for the new test framework. For backward compatibility with scripts and muscle memory, <code>run-test</code> (and variants like <code>exploded-run-test</code> or <code>run-test-tier1</code>) are kept as aliases.</p> <p>Some example command-lines:</p> <pre><code>$ make test-tier1 $ make test-jdk_lang JTREG="JOBS=8"
--- a/doc/testing.md Mon Mar 25 20:57:07 2019 +0100 +++ b/doc/testing.md Mon Mar 25 17:29:43 2019 -0400 @@ -12,11 +12,10 @@ instead. Not all tests will run successfully on the exploded image, but using this target can greatly improve rebuild times for certain workflows. -Previously, `make test` was used invoke an old system for running test, and +Previously, `make test` was used to invoke an old system for running tests, and `make run-test` was used for the new test framework. For backward compatibility with scripts and muscle memory, `run-test` (and variants like -`exploded-run-test` or `run-test-tier1`) are kept as aliases. The old system -can still be accessed for some time using `cd test && make`. +`exploded-run-test` or `run-test-tier1`) are kept as aliases. Some example command-lines: