This keywords applies globally to the test runner system. If set to true, it enables JCov coverage reporting for all tests run. To be useful, the JDK under test must be run with a JDK built with JCov instrumentation (configure --with-jcov=<path to directory containing lib/jcov.jar>, make jcov-image).
The simplest way to run tests with JCov coverage report is to use the special target jcov-test instead of test, e.g. make jcov-test TEST=jdk_lang. This will make sure the JCov image is built, and that JCov reporting is enabled.
The JCov report is stored in build/$BUILD/test-results/jcov-output.
The JCov report is stored in build/$BUILD/test-results/jcov-output/report.
Please note that running with JCov reporting can be very memory intensive.
While collecting code coverage with JCov, it is also possible to find coverage for only recently changed code. JCOV_DIFF_CHANGESET specifies a source revision. A textual report will be generated showing coverage of the diff between the specified revision and the repository tip.
diff --git a/doc/testing.md b/doc/testing.md index f3d2a9e2993..0e0495cd869 100644 --- a/doc/testing.md +++ b/doc/testing.md @@ -250,7 +250,7 @@ Please note that running with JCov reporting can be very memory intensive. While collecting code coverage with JCov, it is also possible to find coverage for only recently changed code. JCOV_DIFF_CHANGESET specifies a source revision. A textual report will be generated showing coverage of the diff -between the specified revision and the repository tip. +between the specified revision and the repository tip. The report is stored in `build/$BUILD/test-results/jcov-output/diff_coverage_report` file.