From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:39952) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UEyTO-0003zF-LK for qemu-devel@nongnu.org; Mon, 11 Mar 2013 04:52:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UEyTM-00018F-K1 for qemu-devel@nongnu.org; Mon, 11 Mar 2013 04:52:46 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50676) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UEyTM-000185-CG for qemu-devel@nongnu.org; Mon, 11 Mar 2013 04:52:44 -0400 Date: Mon, 11 Mar 2013 14:22:36 +0530 From: Amit Shah Message-ID: <20130311085236.GA979@amit.redhat.com> References: <20130305101154.GA13737@amit.redhat.com> <5136151E.5050206@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5136151E.5050206@redhat.com> Subject: Re: [Qemu-devel] The state of testing List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Lucas Meneghel Rodrigues Cc: Kevin Wolf , Anthony Liguori , Juan Quintela , qemu-devel , Stefan Hajnoczi , Michael Roth , Markus Armbruster On (Tue) 05 Mar 2013 [12:54:06], Lucas Meneghel Rodrigues wrote: > On 03/05/2013 07:11 AM, Amit Shah wrote: > >On (Mon) 04 Mar 2013 [16:53:55], Stefan Hajnoczi wrote: > >>How are things looking with device emulation, migration, monitor, char, etc? > > > >I have a few tests coded up for virtio-serial at > > > >http://fedorapeople.org/cgit/amitshah/public_git/test-virtserial.git/ > > > >which indirectly test chardevs. > > > >Autotest (virt-tests) also has virtio-serial tests which end up > >testing chardevs. > > >chardevs, being an external interface to qemu, do get tested whenever > >anyone starts qemu with e.g. libvirt. > > > >Also, autotest has libvirt-based tests, which exercise the monitor. > >However, I don't think there's anything comprehensive anywhere. > > The virtio console tests span over 130 tests, and take ~4 hours to > run, I'd consider they are comprehensive. It's a commendable job the folks who've put together the tests have done. However, it's still not comprehensive for the chardevs themselves. For example, guest freezes for lack of flow control would've been flagged by autotest otherwise. Though I'm happy to now note that will no longer be an issue on qemu.git, and we must now add tests for checking flow control. Amit