devel/testing/main.rst

9 tests you can run ``make check-help`` from either the source or build
37 Testing with "make check"
40 The "make check" testing family includes most of the C based tests in QEMU.
46   make check
49 Different sub-types of "make check" tests will be explained below.
68 In QEMU, unit tests can be invoked with ``make check-unit``. They are
96 ``gdb``. However there can still be differences in behavior between ``make``
103   make check-unit V=1
120    make check-qtest
184 ``make check-block`` runs a subset of the block layer iotests (the tests that
195 than "make check" tests and 99% of the code is written in bash or Python
199 To run iotests, make sure QEMU is built successfully, then switch to the
251 * A Bash script. It will make use of several environmental variables related
349 - auto: Tests in this group are used during "make check" and should be
383 on your development machine, then make sure you have the privilege to run
425 From source tree, type ``make docker-help`` to see the help. Testing
427 ``make`` are done in the container, with parameters defined by the
428 make target):
432   make docker-test-build@debian
450    make docker-image-debian-arm64-cross NOCACHE=1
456 in ``tests/docker/dockerfiles/``, called ``debian.docker``. ``make docker-help``
462 for example, to make qemu-user powered cross build containers work.
488 ``tests/lcitool/projects/qemu.yml`` in order to make the dependency
496  * Run ``make lcitool-refresh`` to re-generate all relevant build environment
522    run ``make lcitool-refresh``.
525    for as many OS distros as practical to make sure that there are no
594 The full list of tests is printed in the ``make docker-help`` help.
603    ``make docker-test-mingw@fedora-win64-cross J=8``.
617 list is in the ``make docker`` help text. The frequently used ones are:
619 * ``V=1``: the same as in top level ``make``. It will be propagated to the
621 * ``J=$N``: the number of parallel tasks in make commands in the container,
622   similar to the ``-j $N`` option in top level ``make``. (The ``-j`` option in
623   top level ``make`` will not be propagated into the container.)
641 The test-tsan test will build using TSan and then run make check.
645   make docker-test-tsan@ubuntu2204
780   make docker-binfmt-image-debian-sid-hppa \
797 help which is displayed with ``make vm-help``.
802 Run ``make vm-help`` to list available make targets. Invoke a specific make
803 command to run build test in an image. For example, ``make vm-build-freebsd``
823 Make jobs
826 The ``-j$X`` option in the make command line is not propagated into the VM,
827 specify ``J=$X`` to control the make jobs in the guest.
832 Add ``DEBUG=1`` and/or ``V=1`` to the make command to allow interactive
834 ``V=1`` will be propagated down into the make jobs in the guest.
890   QEMU source tree, then configure/build it. Running "make check" is also
918   make check-functional
924 Testing with "make check-tcg"
962   make build-tcg-tests-$TARGET
966   make run-tcg-tests-$TARGET
975 run ``make help`` from the test build directory you will get a list of
979   make run-plugin-test-mmap-with-libinline.so
1025 If you want to gather coverage information on a single test the ``make
1029 You can generate a HTML coverage report by executing ``make