Lines Matching +full:crash +full:- +full:test +full:- +full:debian
1 .. _checkavocado-ref:
27 * Interact with external data files that accompany the test itself
36 * Make use of various other test related utilities available at the
37 test class itself and at the utility library:
39 - http://avocado-framework.readthedocs.io/en/latest/api/test/avocado.html#avocado.Test
40 - http://avocado-framework.readthedocs.io/en/latest/api/utils/avocado.utils.html
43 -------------
49 make check-avocado
52 necessary avocado-framework dependencies into the QEMU venv within the
53 build tree (at ``./pyvenv``). Test results are also saved within the
58 ``configure`` is called with ``--python=`` and that those modules are
59 available. On Debian and Ubuntu based systems, depending on the
60 specific version, they may be on packages named ``python3-venv`` and
61 ``python3-pip``.
64 ``make check-avocado`` command and the ``AVOCADO_TAGS`` environment
69 make check-avocado AVOCADO_TAGS=quick
75 https://avocado-framework.readthedocs.io/en/latest/guides/user/chapters/tags.html
77 To run a single test file, a couple of them, or a test within a file
78 using the ``make check-avocado`` command, set the ``AVOCADO_TESTS``
79 environment variable with the test files or test names. To run all
84 make check-avocado AVOCADO_TESTS=$FILEPATH
86 The same is valid to run tests from multiple test files:
90 make check-avocado AVOCADO_TESTS='$FILEPATH1 $FILEPATH2'
92 To run a single test within a file, use:
96 make check-avocado AVOCADO_TESTS=$FILEPATH:$TESTCLASS.$TESTNAME
98 The same is valid to run single tests from multiple test files:
102 …make check-avocado AVOCADO_TESTS='$FILEPATH1:$TESTCLASS1.$TESTNAME1 $FILEPATH2:$TESTCLASS2.$TESTNA…
105 without an "activation". For instance, the Avocado test runner
112 Note that if ``make check-avocado`` was not executed before, it is
118 make check-venv
120 It is also possible to run tests from a single file or a single test within
121 a test file. To run tests from a single file within the build tree, use:
127 To run a single test within a test file, use:
133 Valid test names are visible in the output from any previous execution
134 of Avocado or ``make check-avocado``, and can also be queried using:
141 -------------------
147 pip install --user avocado-framework
151 https://avocado-framework.readthedocs.io/en/latest/guides/user/chapters/installing.html
154 --------
171 res = self.vm.cmd('human-monitor-command',
175 To execute your test, run:
187 avocado run -t quick .
189 The ``avocado_qemu.QemuSystemTest`` base test class
195 First of all, it attempts to give each test a ready to use QEMUMachine
198 is left to the test writer.
200 The base test class has also support for tests with more than one
223 'human-monitor-command',
227 'human-monitor-command',
231 'human-monitor-command',
236 At test "tear down", ``avocado_qemu.QemuSystemTest`` handles all the
239 The ``avocado_qemu.LinuxTest`` base test class
258 def test(self):
266 -----------
269 device-crash-test and other Python scripts. It's a wrapper around the
291 Based on this description, test writers will usually rely on one of
297 "qemu-system-${arch}", either in the current
304 -------------------
306 Test section in Attribute reference
310 ``avocado.Test`` class, the following attributes are available on any
323 the framework or by the test itself. At the framework level, it will
328 A test may, for instance, use the same value when selecting the
331 The ``arch`` attribute will be set to the test parameter of the same
333 ``None``, or, if the test is tagged with one (and only one)
340 by the test.
342 The ``cpu`` attribute will be set to the test parameter of the same
344 ``None ``, or, if the test is tagged with one (and only one)
351 by the test.
353 The ``machine`` attribute will be set to the test parameter of the same
355 ``None``, or, if the test is tagged with one (and only one)
375 test. The name should match the **Provider** column on the list
378 https://avocado-framework.readthedocs.io/en/latest/guides/writer/libs/vmimage.html#supported-images
384 test. The name should match the **Version** column on the list
387 https://avocado-framework.readthedocs.io/en/latest/guides/writer/libs/vmimage.html#supported-images
392 The sha256 hash of the guest image file used for the test.
394 If this value is not set in the code or by a test parameter (with the
399 -------------------
404 …https://avocado-framework.readthedocs.io/en/latest/guides/writer/chapters/writing.html#accessing-t…
411 PARAMS (key=qemu_bin, path=*, default=./qemu-system-x86_64) => './qemu-system-x86_64
413 Test section in Parameter reference
423 A test may, for instance, use the same value when selecting the
433 by the test.
439 by the test.
456 test. The name should match the **Provider** column on the list
459 https://avocado-framework.readthedocs.io/en/latest/guides/writer/libs/vmimage.html#supported-images
465 test. The name should match the **Version** column on the list
468 https://avocado-framework.readthedocs.io/en/latest/guides/writer/libs/vmimage.html#supported-images
473 The sha256 hash of the guest image file used for the test.
479 --------------
483 on the test system or when the running environment is a CI system. For further
486 …https://avocado-framework.readthedocs.io/en/latest/guides/writer/chapters/writing.html#skipping-te…
509 usefulness of the test too. A unique test is worth spending more time on,
511 a test or set of similar tests which take more than 100 seconds to
528 test suite of getting stuck. The timeout value can be set via test parameter or
529 property defined in the test class, for further details::
531 …https://avocado-framework.readthedocs.io/en/latest/guides/writer/chapters/writing.html#setting-a-t…
533 Even though the timeout can be set by the test developer, there are some tests
534 that may not have a well-defined limit of time to finish under certain
545 similar situation then raise a bug and then mark the test as shown on
550 # See https://gitlab.com/qemu-project/qemu/-/issues/nnnn
551 @skipUnless(os.getenv('QEMU_TEST_FLAKY_TESTS'), 'Test is unstable on GitLab')
552 def test(self):
555 You can also add ``:avocado: tags=flaky`` to the test meta-data so
561 run tests/avocado -filter-by-tags=flaky
568 --------------------
574 pip list --user
580 If you've used ``make check-avocado``, the Python virtual environment where
581 Avocado is installed will be cleaned up as part of ``make check-clean``.