devel/testing/functional.rst

1 .. _checkfunctional-ref:
17 Note that if you don't use one of the QemuBaseTest based classes for your
19 that there is no TAP-incompatible output written to stdio, e.g. either by
24 Tests based on ``qemu_test.QemuSystemTest`` can easily:
36  * Download (and cache) remote data files, such as firmware and kernel
40 -------------
46   make check-functional
53   make check-functional-x86_64
63   $ export QEMU_TEST_QEMU_BINARY=$PWD/qemu-system-x86_64
73 -------
91 -----------------------------
107           res = self.vm.cmd('human-monitor-command',
116 can also be run stand-alone, without a test runner. OTOH when run via a test
154               'human-monitor-command',
158               'human-monitor-command',
162               'human-monitor-command',
171 -----------
174 device-crash-test and other Python scripts.  It's a wrapper around the
202 to a UNIX socket name. The ``qmp-shell`` command can then be
206 -------------------
239 qemu-system-* binaries.
263 --------------
266 firmware images, etc.) from the internet to be able to run tests with
277 run only ``make check-functional``, the "thorough" tests will be
281   make -j$(nproc) check SPEED=thorough
288 the tests are run. This pre-caching is done with the qemu_test.Asset
304 The pre-caching will be done automatically when running
305 ``make check-functional`` (but not when running e.g.
306 ``make check-functional-<target>``). In case you just want to download
309     make precache-functional
316 --------------
318 Since the test framework is based on the common Python unittest framework,
324   https://docs.python.org/3/library/unittest.html#skipping-tests-and-expected-failures
343 There are tests which will boot a kernel image or firmware that can be
363   # See https://gitlab.com/qemu-project/qemu/-/issues/nnnn