On 14/01/21 21:13, Sean Christopherson wrote:
On Wed, Jan 13, 2021, Paolo Bonzini wrote:
On 12/01/21 23:28, Sean Christopherson wrote:
What's the biggest hurdle for doing this completely within the unit test
framework? Is teaching the framework to migrate a unit test the biggest pain?
Yes, pretty much. The shell script framework would show its limits.
That said, I've always treated run_tests.sh as a utility more than an
integral part of kvm-unit-tests. There's nothing that prevents a more
capable framework from parsing unittests.cfg.
Heh, got anyone you can "volunteer" to create a new framework? One-button
migration testing would be very nice to have. I suspect I'm not the only
contributor that doesn't do migration testing as part of their standard workflow.
avocado-vt is the one I use for installation tests. It can do a lot
more, including migration, but it is a bit hard to set up.
avocado-qemu (python/qemu and tests/acceptance in the QEMU tree) is a
lot simpler, but it does not have a lot of tests and in particular it is
not integrated with kvm-unit-tests.
Maxim also wrote a script to automate his tests which has quite a few
features, but I've never used it myself.
Paolo
