devel/testing/functional.rst

1 .. _checkfunctional-ref:
9 The functional tests have initially evolved from the Avocado tests, so there
10 is a lot of similarity to those tests here (see :ref:`checkavocado-ref` for
11 details about the Avocado tests).
22 that there is no TAP-incompatible output written to stdio, e.g. either by
39  * Download (and cache) remote data files, such as firmware and kernel
43 -------------
49   make check-functional
56   make check-functional-x86_64
66   $ export QEMU_TEST_QEMU_BINARY=$PWD/qemu-system-x86_64
76 -------
94 -----------------------------
110           res = self.vm.cmd('human-monitor-command',
119 can also be run stand-alone, without a test runner. OTOH when run via a test
157               'human-monitor-command',
161               'human-monitor-command',
165               'human-monitor-command',
174 -----------
177 device-crash-test and other Python scripts.  It's a wrapper around the
205 to a UNIX socket name. The ``qmp-shell`` command can then be
209 -------------------
242 qemu-system-* binaries.
266 --------------
280 run only run ``make check-functional``, the "thorough" tests will be
284   make -j$(nproc) check SPEED=thorough
291 the tests are run. This pre-caching is done with the qemu_test.Asset
307 The pre-caching will be done automatically when running
308 ``make check-functional`` (but not when running e.g.
309 ``make check-functional-<target>``). In case you just want to download
312     make precache-functional
314 The cache is populated in the ``~/.cache/qemu/download`` directory by
319 --------------
327   https://docs.python.org/3/library/unittest.html#skipping-tests-and-expected-failures
366   # See https://gitlab.com/qemu-project/qemu/-/issues/nnnn