From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:43891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S5fUJ-0004FY-WF for qemu-devel@nongnu.org; Thu, 08 Mar 2012 10:42:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S5fUI-0002Zk-24 for qemu-devel@nongnu.org; Thu, 08 Mar 2012 10:42:43 -0500 Received: from mx1.redhat.com ([209.132.183.28]:1027) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S5fUH-0002ZZ-Q3 for qemu-devel@nongnu.org; Thu, 08 Mar 2012 10:42:41 -0500 Message-ID: <4F58D441.60106@redhat.com> Date: Thu, 08 Mar 2012 16:46:09 +0100 From: Kevin Wolf MIME-Version: 1.0 References: <4F582EDB.1040608@redhat.com> <4F58B5CB.8040503@codemonkey.ws> <20120308144958.GA25750@t420s.optimusnet> <4F58C897.5020405@codemonkey.ws> In-Reply-To: <4F58C897.5020405@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC] Future goals for autotest and virtualization tests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Lucas Meneghel Rodrigues , QEMU devel , Scott Zawalski , Cleber Rosa , "kvm-autotest@redhat.com" , Ademar Reis Am 08.03.2012 15:56, schrieb Anthony Liguori: >> I particularly agreed with basically everything you said on that >> discussion regarding test simplification (I had just joined the >> team back then). To me, autotest has been focusing on QE-level, >> leaving the developer-level test requirements out. Now we're >> attacking this new front, and a lot of the requirements are >> indeed from that discussion. > > If you want to talk about this in terms of "requirements", my requirement is for > "developer-level" tests to live in qemu.git and be integrated into make check. Actually, I think make check should be something that runs _really_ quickly. We'll probably want another make check-full or something that runs more extensive tests. That's the reason why the patch I proposed earlier today runs only a few qemu-iotests cases during make check. The whole thing would already take too long for everyone to use it. If people run some quick sanity tests for all of qemu plus the full tests in the subsystem in which they're making changes, I think that would be the best we can realistically expect. Kevin