The same way the arch tag is being used as a fallback for the arch parameter, let's do the same for QEMU's machine and avoid some boiler plate code. This is now possible because, since Avocado 72.0, it's possible to use tags with names that match the machine types on QEMU. Signed-off-by: Cleber Rosa <crosa@redhat.com> Message-Id: <20191104151323.9883-4-crosa@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Signed-off-by: Cleber Rosa <crosa@redhat.com> |
||
---|---|---|
.. | ||
avocado_qemu | ||
boot_linux_console.py | ||
cpu_queries.py | ||
empty_cpu_model.py | ||
linux_initrd.py | ||
linux_ssh_mips_malta.py | ||
machine_m68k_nextcube.py | ||
machine_sparc_leon3.py | ||
migration.py | ||
pc_cpu_hotplug_props.py | ||
ppc_prep_40p.py | ||
README.rst | ||
version.py | ||
virtio_version.py | ||
vnc.py | ||
x86_cpu_model_versions.py |
============================================ Acceptance tests using the Avocado Framework ============================================ This directory contains functional tests, also known as acceptance level tests. They're usually higher level, and may interact with external resources and with various guest operating systems. For more information, please refer to ``docs/devel/testing.rst``, section "Acceptance tests using the Avocado Framework".