[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [ANNOUNCE] qemu-test: a set of tests scripts for QEMU

From: Anthony Liguori
Subject: Re: [Qemu-devel] [ANNOUNCE] qemu-test: a set of tests scripts for QEMU
Date: Thu, 29 Dec 2011 11:11:44 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15

On 12/29/2011 11:06 AM, Avi Kivity wrote:
On 12/29/2011 07:02 PM, Anthony Liguori wrote:

Those are rare occurrences and have always been a bit awkward.  OTOH,
we're talking about the critical path of essentially every single
feature that gets merged into QEMU.

Won't that be qtest?

The difference is that the qtest test can be patch N/N in a patch series and be merged at exactly the same time.

I think having an in-tree test suite is the only practical way to do TDD.


Anthony Liguori

Let's consider postcopy live migration being proposed.  In addition to
various unit tests, it also wants an integration test.  So now we need
to write a qemu-test postcopy live migration test, and also autotest
test that tests non-Linux guests, migration under load, with memory
hotplug, etc.

But the integration test is also going to depend on libvirt support
for the feature.  So how does this all get orchestrated?  kvm-autotest
merges the test case first, then QEMU merges the support, then
libvirt?  What about VDSM and ovirt-engine?  Once kvm-autotest starts
supporting VDSM that's yet another component to deal with.

Realistically, kvm-autotest is going to have to wait for the bits to
get merged in all of the necessary pieces and then build a test for it
on their own schedule.

It just has to be posted and reviewed, it doesn't all have to be merged
at the same time (and the qemu merge has to precede the autotest merge)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]