diff options
author | Alex Bennée | 2018-06-20 13:34:45 +0200 |
---|---|---|
committer | Alex Bennée | 2018-07-05 16:59:41 +0200 |
commit | 990e6a2754fc16501470b661c4af94ec036f1190 (patch) | |
tree | cb3a68604a18721982ed5de7512cc4fa63df5327 /docs/devel | |
parent | travis: add gcovr summary for GCOV build (diff) | |
download | qemu-990e6a2754fc16501470b661c4af94ec036f1190.tar.gz qemu-990e6a2754fc16501470b661c4af94ec036f1190.tar.xz qemu-990e6a2754fc16501470b661c4af94ec036f1190.zip |
build-system: add clean-coverage target
This can be used to remove any stale coverage data before any
particular test run. This is useful for analysing individual tests.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Tested-by: Philippe Mathieu-Daudé <f4bug@amsat.org>---
Diffstat (limited to 'docs/devel')
-rw-r--r-- | docs/devel/testing.rst | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst index 66ef219f69..7f04ca104e 100644 --- a/docs/devel/testing.rst +++ b/docs/devel/testing.rst @@ -161,9 +161,14 @@ GCC gcov support ``gcov`` is a GCC tool to analyze the testing coverage by instrumenting the tested code. To use it, configure QEMU with ``--enable-gcov`` option and build. Then run ``make check`` as usual. -Reports can be obtained by running ``gcov`` command on the output -files under ``$build_dir/tests/``, please read the ``gcov`` -documentation for more information. + +If you want to gather coverage information on a single test the ``make +clean-coverage`` target can be used to delete any existing coverage +information before running a single test. + +Reports can be obtained by running ``gcov`` command +on the output files under ``$build_dir/tests/``, please read the +``gcov`` documentation for more information. QEMU iotests ============ |