--- old/doc/testing.html 2018-11-01 16:34:09.000000000 -0700 +++ new/doc/testing.html 2018-11-01 16:34:08.000000000 -0700 @@ -62,9 +62,8 @@
If you want, you can single out an individual test or a group of tests, for instance gtest:LogDecorations
or gtest:LogDecorations.level_test_vm
. This can be particularly useful if you want to run a shaky test repeatedly.
For Gtest, there is a separate test suite for each JVM variant. The JVM variant is defined by adding /<variant>
to the test descriptor, e.g. gtest:Log/client
. If you specify no variant, gtest will run once for each JVM variant present (e.g. server, client). So if you only have the server JVM present, then gtest:all
will be equivalent to gtest:all/server
.
A handful of odd tests that are not covered by any other testing framework are accessible using the special:
test descriptor. Currently, this includes hotspot-internal
, failure-handler
and make
.
A handful of odd tests that are not covered by any other testing framework are accessible using the special:
test descriptor. Currently, this includes failure-handler
and make
.
Hotspot legacy internal testing (run using -XX:+ExecuteInternalVMTests
) is run using special:hotspot-internal
or just hotspot-internal
as test descriptor, and will only work on a debug JVM.
Failure handler testing is run using special:failure-handler
or just failure-handler
as test descriptor.
Tests for the build system, including both makefiles and related functionality, is run using special:make
or just make
as test descriptor. This is equivalent to special:make:all
.
A specific make test can be run by supplying it as argument, e.g. special:make:idea
. As a special syntax, this can also be expressed as make-idea
, which allows for command lines as make test-make-idea
.