mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-17 07:02:03 -06:00
docs: move gcov section at the end of testing.rst
gcov testing applies to all tests, not just make check. Move it out of the make check section. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
parent
e9adb4ace2
commit
9fce360176
1 changed files with 19 additions and 19 deletions
|
@ -114,25 +114,6 @@ check-block
|
||||||
are in the "auto" group).
|
are in the "auto" group).
|
||||||
See the "QEMU iotests" section below for more information.
|
See the "QEMU iotests" section below for more information.
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
If you want to gather coverage information on a single test the ``make
|
|
||||||
clean-gcda`` target can be used to delete any existing coverage
|
|
||||||
information before running a single test.
|
|
||||||
|
|
||||||
You can generate a HTML coverage report by executing ``make
|
|
||||||
coverage-html`` which will create
|
|
||||||
``meson-logs/coveragereport/index.html``.
|
|
||||||
|
|
||||||
Further analysis can be conducted by running the ``gcov`` command
|
|
||||||
directly on the various .gcda output files. Please read the ``gcov``
|
|
||||||
documentation for more information.
|
|
||||||
|
|
||||||
QEMU iotests
|
QEMU iotests
|
||||||
============
|
============
|
||||||
|
|
||||||
|
@ -1302,3 +1283,22 @@ exercise as many corner cases as possible. It is a useful test suite
|
||||||
to run to exercise QEMU's linux-user code::
|
to run to exercise QEMU's linux-user code::
|
||||||
|
|
||||||
https://linux-test-project.github.io/
|
https://linux-test-project.github.io/
|
||||||
|
|
||||||
|
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 the tests as usual.
|
||||||
|
|
||||||
|
If you want to gather coverage information on a single test the ``make
|
||||||
|
clean-gcda`` target can be used to delete any existing coverage
|
||||||
|
information before running a single test.
|
||||||
|
|
||||||
|
You can generate a HTML coverage report by executing ``make
|
||||||
|
coverage-html`` which will create
|
||||||
|
``meson-logs/coveragereport/index.html``.
|
||||||
|
|
||||||
|
Further analysis can be conducted by running the ``gcov`` command
|
||||||
|
directly on the various .gcda output files. Please read the ``gcov``
|
||||||
|
documentation for more information.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue