Re: [Qemu-devel] Suggestion for testing framework

[Anthony Liguori]

Glauber Costa wrote:
> On Tue, Jun 3, 2008 at 7:02 PM, Paul Brook <address@hidden> wrote:
>   
> > On Tuesday 03 June 2008, Erik de Castro Lopo wrote:
> >     
> > > Balazs Attila-Mihaly (Cd-MaN) wrote:
> > >       
> > > > Hello all
> > > >
> > > > It seems that there is agreement that some sort of automated
> > > > testing is "a good thing" ;-).
> > > >         
> > > I am a huge fan of testing and think that qemu developers and users
> > > would both benefit from more automated testing.
> > >       
> > IMHO Automated testing by itself is pretty much worthless.
> > The value comes from having someone look at the results, and actively fix
> > problems as they are discovered. Once you've allocated resources to do this
> > bugfixing setting up the testing is fairly trivial.
> >     
>
> Not at all. A developer writing something new for qemu will have a way
> to make sure his code works before submitting it upstream.
>   

Test cases are great.  I think the question is how useful is a fully 
automated testing suite that runs continuously.  Without people 
dedicating time to track down all of the various failures, it tends to 
suffer the same fate as a poorly maintained bugzilla.

But yeah, we want reproducible test cases.  That's what KVMTest is all 
about--automating things that normally require user intervention.

Regards,

Anthony Liguori

> Right now, each one has to write its own testing, each time, which can
> be failed in itself, and not do a full coverage.
>
> So while it may not do much for existing code, it can certainly help
> the quality of new code to improve.
>
>
>