On Thu, Jan 14, 2021 at 12:13:22PM -0800, 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. > We have one-button migration tests already with kvm-unit-tests. Just compile the tests that use the migration framework as standalone tests and then run them directly. I agree, though, that Bash is a pain for some of the stuff we're trying to do. However, we do have requests to keep the framework written in Bash, because KVM testing is regularly done with simulators and even in embedded environments. It's not desirable, or even possible, to have e.g. Python everywhere we want kvm-unit-tests. Thanks, drew
