autotest (was Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions)

[Dor Laor <dlaor@redhat.com>]

Anthony Liguori wrote:
> Glauber Costa wrote:    
>> How about we start sending patches to the list? Then this kind of 
>> thing can be avoided.
>>   
>
> It doesn't magically solve the problem.  I post most patches and still 
> regressions slip in.  I review every patch I commit and still 
> regressions slip in.  People are imperfect.
>
> The best way to prevent regressions is to have an automated test suite 
> that everyone can use to validate that a series of patches doesn't 
> break things.
We have such a frame work, it's the kvm autotest project - 
http://www.linux-kvm.org/page/KVM-Autotest.
It is used currently by Avi for his tree + to test more internal trees. 
It recently catched a regression with -net usage.
Don't let its name fool you, it should be able to test bare qemu code 
too. Also we are finally on track for
merging the changes upstream towards autotest project.

So ideally, what we need for qemu project is:
1. Make kvm-autotest work with qemu only
    - It's mainly about changing timeouts and better, move to kickstart 
files
2. Have qemu community use it and contribute to it.
3. Maintainers should ...
    - Well, I'll let you maintainers complete that line :)

#1 will surely happen soon. I hope #2, #3 will join right after, making 
qemu head/stable a better place.
Regards,
Dor