Re: [Xen-tools] Testing xm

To:	Anthony Liguori <aliguori@xxxxxxxxxx>
Subject:	Re: [Xen-tools] Testing xm
From:	Dan Smith <danms@xxxxxxxxxx>
Date:	Sat, 27 Aug 2005 08:34:24 -0700
Cc:	xen-tools@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Sat, 27 Aug 2005 15:32:37 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<430E305B.7070507@xxxxxxxxxx> (Anthony Liguori's message of "Thu, 25 Aug 2005 15:55:55 -0500")
List-help:	<mailto:xen-tools-request@lists.xensource.com?subject=help>
List-id:	Xen control tools developers <xen-tools.lists.xensource.com>
List-post:	<mailto:xen-tools@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-tools>, <mailto:xen-tools-request@lists.xensource.com?subject=unsubscribe>
References:	<m3u0hdg4kc.fsf@xxxxxxxxxxxxxxxxxxxxxxxx> <430E305B.7070507@xxxxxxxxxx>
Sender:	xen-tools-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux)

AL> Excellent!  Could this be submitted as a patch to the Xen tree?
AL> So that we could run a top-level make check and do some basic
AL> testing?

Sure, I can work something up next week.

While working on the xm interface changes, I've been thinking how nice
it would be to have tests for each command to verify that it still
works as it should after renaming everything.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx


_______________________________________________
Xen-tools mailing list
Xen-tools@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-tools

WARNING - OLD ARCHIVES

xen-tools

Re: [Xen-tools] Testing xm