From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: george.dunlap@eu.citrix.com, xen-devel@lists.xensource.com
Subject: Re: [PATCH v2 0/4] raisin: introduce tests
Date: Tue, 5 May 2015 12:59:27 +0100 [thread overview]
Message-ID: <1430827167.2660.64.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1505011646230.2640@kaball.uk.xensource.com>
On Fri, 2015-05-01 at 16:48 +0100, Stefano Stabellini wrote:
> Hi all,
>
> this patch series introduces a framework to execute simple unit and
> functional tests in raisin. It can be used by developers to validate
> their changes before submitting a patch series to xen-devel. It can also
> be used by OSSTest to test for regressions on one particular
> functionality. This patch series only introduces two tests: a PV guest
> creation test and an HVM guest creation test. They are both based on
> busybox. More tests will follow.
What is the intended scope of these tests? e.g. when should a test be
added here rather than to osstest? Do you eventually plan to have an
osstest job which executes the raisin tests?
Ian.
next prev parent reply other threads:[~2015-05-05 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 15:48 [PATCH v2 0/4] raisin: introduce tests Stefano Stabellini
2015-05-01 15:48 ` [PATCH v2 1/4] " Stefano Stabellini
2015-05-01 15:48 ` [PATCH v2 2/4] raisin: add an hvm test Stefano Stabellini
2015-05-01 15:48 ` [PATCH v2 3/4] raisin: improve output Stefano Stabellini
2015-05-01 15:48 ` [PATCH v2 4/4] raisin: small stlye improvement in for_each_component Stefano Stabellini
2015-05-05 11:59 ` Ian Campbell [this message]
2015-05-05 13:55 ` [PATCH v2 0/4] raisin: introduce tests Stefano Stabellini
2015-05-06 14:29 ` George Dunlap
2015-05-06 14:39 ` Stefano Stabellini
2015-05-06 14:46 ` Ian Campbell
2015-05-06 15:11 ` George Dunlap
2015-05-06 15:26 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1430827167.2660.64.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.