From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M8sz4-00036v-32 for qemu-devel@nongnu.org; Tue, 26 May 2009 05:30:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M8syz-00036j-Jz for qemu-devel@nongnu.org; Tue, 26 May 2009 05:30:09 -0400 Received: from [199.232.76.173] (port=49658 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M8syz-00036g-Bo for qemu-devel@nongnu.org; Tue, 26 May 2009 05:30:05 -0400 Received: from mail-gx0-f176.google.com ([209.85.217.176]:48098) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M8syy-0001NG-VT for qemu-devel@nongnu.org; Tue, 26 May 2009 05:30:05 -0400 Received: by gxk24 with SMTP id 24so8951591gxk.10 for ; Tue, 26 May 2009 02:30:04 -0700 (PDT) Message-ID: <4A1BB698.7080805@codemonkey.ws> Date: Tue, 26 May 2009 04:30:00 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: autotest (was Re: [Qemu-devel] Re: [Qemu-commits] [COMMIT f80f9ec] Convert machine registration to use module initfunctions) References: <200905211348.n4LDmnYd025976@d01av04.pok.ibm.com> <200905212336.02493.paul@codesourcery.com> <20090521225039.GA26811@poweredge.glommer> <4A160138.7050109@us.ibm.com> <4A18068F.5020700@redhat.com> <4A19A422.80807@us.ibm.com> <4A19B32E.2020201@redhat.com> <4A1BA408.5030400@us.ibm.com> <4A1BB3C4.5090002@redhat.com> In-Reply-To: <4A1BB3C4.5090002@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dlaor@redhat.com Cc: Anthony Liguori , Glauber Costa , qemu-devel@nongnu.org, Paul Brook , Avi Kivity Dor Laor wrote: > Anthony Liguori wrote: >> Avi Kivity wrote: >>> Anthony Liguori wrote: >>>> Autotest doesn't currently test the regressions that I want to test. >>> >>> Which regressions do you want to test? >> >> For instance, we often have networking regressions. In particular, >> with the refactoring going on in slirp and tun/tap, I'd really like >> to have an automated way to test slirp and tap with TCP >> transmit/receive, and slirp redir. I have something locally to do >> this that I intend on posting in the next few days. >> > Current kvm autotest do test slirp. The step-files for guest > installation open ssh/telnet access in order > to let the host reach them. > We trapped exactly this regression using autotest. What I want is a single test that completes quickly. This means a preconfigured guest that I can run a quick test case against. Installation tests a lot of things. I'm looking for more targeted tests. >> I wouldn't require kvm-autotest, but I'd like to have an interest set >> of unit tests that are then usable within kvm-autotest. Once we have >> that, asking politely for tests to be written I think is quite >> reasonable. > Some features are easily tested using a large framework, for example > migration, slirp, time drift, etc. > In addition kvm's tests unit tests, qemu-io and similar should be > written too in order to test various cases that > are only reasonable to be found using low level operations. > No doubt all of the unit tests should be executed from autotest. Yup, I agree 100%. Regards, Anthony Liguori