From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Call to write tests for osstest Date: Wed, 14 Aug 2013 14:52:31 +0100 Message-ID: <520B8B9F.3080006@eu.citrix.com> References: <20130808194044.GE4513@konrad-lan.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130808194044.GE4513@konrad-lan.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 08/08/13 20:40, Konrad Rzeszutek Wilk wrote: > On Thu, Aug 08, 2013 at 05:01:01PM +0100, George Dunlap wrote: >> As release coordinator, and therefore de-facto >> tracker-of-bugs-and-regressions, it seems to me that one of the >> shortcomings in our current development mode is a lack of good >> regression testing for many of the less common, but still very >> important features of Xen; things like S3, driver domains, nested >> virt, and so on. >> >> We do have a regression-testing push gate for the xen trees, written >> by Ian Jackson, called osstest, with a lot of great functionality, >> including a test scheduler, an automatic Baysean bisector, and so on. >> Apart from more hardware, it is mainly lacking a more complete set of >> tests. >> >> The Xen Project team here at Citrix agreed with me, and have decided >> during the 4.4 timeframe to take on the task of adding some important >> functional tests to osstest; our list is below. We'd love for you to >> join us. >> >> I will be tracking the implementation of the tests as part of the >> regular 4.4 release updates. I encourage people to join us by >> thinking about a particular feature or bit of functionality that is >> not yet tested by osstest, which you would like to see implemented in >> the 4.4 timeframe, and responding to this e-mail, or one of the >> regular development update e-mails asking it to be added. >> >> There is a description of osstest, along with a link to the source code, here: >> >> http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-osstest/ >> >> === Testing coverage === >> >> * Network driver domains >> @George >> >> * new libxl w/ previous versions of xl >> @IanJ >> >> * Host S3 suspend >> @bguthro? >> >> * Default [example] XSM policy >> @Stefano to ask Daniel D >> >> * Xen on ARM >> # problem ATM: hardware >> @ianc >> emulator: @stefano to think about it >> >> * Storage driver domains >> @roger >> >> * HVM pci passthrough >> @anthony > PV pci passthrough would be nice too. > > You can assign me to it, thought I would need some help in groking the > osstest thingy. Maybe I will just copy what @anthony is doing. I was thinking that would be a subset of the Network driver domains -- but I'll add it on here, and whoever gets to it first can do it. :-) -George