Open Andrei-Stepanov opened 9 years ago
We have main config file:
/var/lib/avocado/data/avocado-vt/backends/qemu/cfg/tests.cfg
Command print tons of possible tests: ./virttest/cartesian_config.py /var/lib/avocado/data/avocado-vt/backends/qemu/cfg/tests.cfg (1*)
It would be fine to know which filters were applied to 1* to get actual tests list (avocado list --vt-type qemu)
Original virt-test has this feature (look at the logs of a ./run execution and you'll see), but I now realize we are not doing that for avocado-vt. I'll work on it as soon as possible.
virt-test
We have main config file:
/var/lib/avocado/data/avocado-vt/backends/qemu/cfg/tests.cfg
Command print tons of possible tests: ./virttest/cartesian_config.py /var/lib/avocado/data/avocado-vt/backends/qemu/cfg/tests.cfg (1*)
It would be fine to know which filters were applied to 1* to get actual tests list (avocado list --vt-type qemu)