devel/testing/functional.rst

1 .. _checkfunctional-ref:
19 that there is no TAP-incompatible output written to stdio, e.g. either by
40 -------------
46   make check-functional
53   make check-functional-x86_64
60 directory should be your build folder. For example::
63   $ export QEMU_TEST_QEMU_BINARY=$PWD/qemu-system-x86_64
73 -------
75 The framework collects log files for each test in the build directory
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 --------------
273 speed mode in the meson.build file, while the "quick" speed mode is
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 --------------
324   https://docs.python.org/3/library/unittest.html#skipping-tests-and-expected-failures
346 usually it means a blob which either its source or build process aren't
354 Some tests are not working reliably and thus are disabled by default.
363   # See https://gitlab.com/qemu-project/qemu/-/issues/nnnn
376 cycles during normal testing, such tests are disabled by default unless