doc/testing.md

rev 50850 : 8205956: Fix usage of "OpenJDK" in build and test instructions

*** 1,11 ****
! % Testing OpenJDK
  
  ## Using the run-test framework
  
  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.
  
  The main target "run-test" uses the jdk-image as the tested product. There is
  also an alternate target "exploded-run-test" that uses the exploded image
--- 1,11 ----
! % Testing the JDK
  
  ## Using the run-test framework
  
  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.
  
  The main target "run-test" uses the jdk-image as the tested product. There is
  also an alternate target "exploded-run-test" that uses the exploded image
*** 59,69 ****
  
  JTReg test groups can be specified either without a test root, e.g. `:tier1`
  (or `tier1`, the initial colon is optional), or with, e.g. `hotspot:tier1`,
  `test/jdk:jdk_util` or `$(TOPDIR)/test/hotspot/jtreg:hotspot_all`. The test
  root can be specified either as an absolute path, or a path relative to the
! OpenJDK top directory, or the `test` directory. For simplicity, the hotspot
  JTReg test root, which really is `hotspot/jtreg` can be abbreviated as
  just `hotspot`.
  
  When specified without a test root, all matching groups from all test roots
  will be added. Otherwise, only the group from the specified test root will be
--- 59,69 ----
  
  JTReg test groups can be specified either without a test root, e.g. `:tier1`
  (or `tier1`, the initial colon is optional), or with, e.g. `hotspot:tier1`,
  `test/jdk:jdk_util` or `$(TOPDIR)/test/hotspot/jtreg:hotspot_all`. The test
  root can be specified either as an absolute path, or a path relative to the
! JDK top directory, or the `test` directory. For simplicity, the hotspot
  JTReg test root, which really is `hotspot/jtreg` can be abbreviated as
  just `hotspot`.
  
  When specified without a test root, all matching groups from all test roots
  will be added. Otherwise, only the group from the specified test root will be
*** 71,81 ****
  
  Individual JTReg tests or directories containing JTReg tests can also be
  specified, like `test/hotspot/jtreg/native_sanity/JniVersion.java` or
  `hotspot/jtreg/native_sanity`. Just like for test root selection, you can
  either specify an absolute path (which can even point to JTReg tests outside
! the source tree), or a path relative to either the OpenJDK top directory or the
  `test` directory. `hotspot` can be used as an alias for `hotspot/jtreg` here as
  well.
  
  As long as the test groups or test paths can be uniquely resolved, you do not
  need to enter the `jtreg:` prefix. If this is not possible, or if you want to
--- 71,81 ----
  
  Individual JTReg tests or directories containing JTReg tests can also be
  specified, like `test/hotspot/jtreg/native_sanity/JniVersion.java` or
  `hotspot/jtreg/native_sanity`. Just like for test root selection, you can
  either specify an absolute path (which can even point to JTReg tests outside
! the source tree), or a path relative to either the JDK top directory or the
  `test` directory. `hotspot` can be used as an alias for `hotspot/jtreg` here as
  well.
  
  As long as the test groups or test paths can be uniquely resolved, you do not
  need to enter the `jtreg:` prefix. If this is not possible, or if you want to