91 ### Gtest
92
93 Since the Hotspot Gtest suite is so quick, the default is to run all tests.
94 This is specified by just `gtest`, or as a fully qualified test descriptor
95 `gtest:all`.
96
97 If you want, you can single out an individual test or a group of tests, for
98 instance `gtest:LogDecorations` or `gtest:LogDecorations.level_test_vm`. This
99 can be particularly useful if you want to run a shaky test repeatedly.
100
101 For Gtest, there is a separate test suite for each JVM variant. The JVM variant
102 is defined by adding `/<variant>` to the test descriptor, e.g.
103 `gtest:Log/client`. If you specify no variant, gtest will run once for each JVM
104 variant present (e.g. server, client). So if you only have the server JVM
105 present, then `gtest:all` will be equivalent to `gtest:all/server`.
106
107 ### Special tests
108
109 A handful of odd tests that are not covered by any other testing framework are
110 accessible using the `special:` test descriptor. Currently, this includes
111 `hotspot-internal`, `failure-handler` and `make`.
112
113 * Hotspot legacy internal testing (run using `-XX:+ExecuteInternalVMTests`)
114 is run using `special:hotspot-internal` or just `hotspot-internal` as test
115 descriptor, and will only work on a debug JVM.
116
117 * Failure handler testing is run using `special:failure-handler` or just
118 `failure-handler` as test descriptor.
119
120 * Tests for the build system, including both makefiles and related
121 functionality, is run using `special:make` or just `make` as test
122 descriptor. This is equivalent to `special:make:all`.
123
124 A specific make test can be run by supplying it as argument, e.g.
125 `special:make:idea`. As a special syntax, this can also be expressed as
126 `make-idea`, which allows for command lines as `make test-make-idea`.
127
128 ## Test results and summary
129
130 At the end of the test run, a summary of all tests run will be presented. This
131 will have a consistent look, regardless of what test suites were used. This is
132 a sample summary:
133
134 ==============================
135 Test summary
|
91 ### Gtest
92
93 Since the Hotspot Gtest suite is so quick, the default is to run all tests.
94 This is specified by just `gtest`, or as a fully qualified test descriptor
95 `gtest:all`.
96
97 If you want, you can single out an individual test or a group of tests, for
98 instance `gtest:LogDecorations` or `gtest:LogDecorations.level_test_vm`. This
99 can be particularly useful if you want to run a shaky test repeatedly.
100
101 For Gtest, there is a separate test suite for each JVM variant. The JVM variant
102 is defined by adding `/<variant>` to the test descriptor, e.g.
103 `gtest:Log/client`. If you specify no variant, gtest will run once for each JVM
104 variant present (e.g. server, client). So if you only have the server JVM
105 present, then `gtest:all` will be equivalent to `gtest:all/server`.
106
107 ### Special tests
108
109 A handful of odd tests that are not covered by any other testing framework are
110 accessible using the `special:` test descriptor. Currently, this includes
111 `failure-handler` and `make`.
112
113 * Failure handler testing is run using `special:failure-handler` or just
114 `failure-handler` as test descriptor.
115
116 * Tests for the build system, including both makefiles and related
117 functionality, is run using `special:make` or just `make` as test
118 descriptor. This is equivalent to `special:make:all`.
119
120 A specific make test can be run by supplying it as argument, e.g.
121 `special:make:idea`. As a special syntax, this can also be expressed as
122 `make-idea`, which allows for command lines as `make test-make-idea`.
123
124 ## Test results and summary
125
126 At the end of the test run, a summary of all tests run will be presented. This
127 will have a consistent look, regardless of what test suites were used. This is
128 a sample summary:
129
130 ==============================
131 Test summary
|