Re: [Qemu-devel] [PATCH 1/2] Add qemu-test for automated testing

[Anthony Liguori <anthony@codemonkey.ws>]

Paul Brook wrote:
> On Wednesday 15 October 2008, Ryan Harper wrote:
>   
>> This patch places the qemu-test framework and tests into the qemu source
>> tree. There are a number of components to this patch:
>>     
>
> Is there any point having this in the qemu repository?
>   

In tree unit testing.  The ideal model would be to have something that 
anyone could run via a "make check" that could confirm whether something 
you've done introduces regressions in things you don't normally test.

> AFAICS it gains nothing from being "integrated" with qemu. It should work 
> equally well with other hypervisors, and even real hardware.
>   

If we're just talking about booting a guest, yeah, I agree.  But even 
the tests introduced here are validating specific QEMU features (like 
migration).  Ideally, this is the type of test that would be added.  
Things like verifying that an emulated USB disk still works, that USB 
hotplug works, that SCSI disks can be mounted in the guest, etc.  If we 
can find a place to host images, it could be automated in such a way 
that images could be easily downloaded.  This would be extremely good 
for doing quick sniff tests of whether or not a change breaks SPARC 
emulation (not that any of us ever do that :-)).

Basically, I think we all end up building this sort of infrastructure on 
our own to be able to do testing so it's a good idea if we all work on 
the same set of tests.

> I'm not saying this is a bad thing, just that is seems like it should be a 
> separate project, and I'd be surprised if such projects don't already exist.
>   

There are separate, more generic test programs like autotest that do 
support QEMU (at least, KVM).  The focus here is more QEMU specific 
unit/regression testing.

Regards,

Anthony Liguori

> Paul
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>