From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Jinjian (Ken)" <jinjian@huawei.com>, xen-devel@lists.xen.org
Cc: john.liuqiming@huawei.com, guoyanjuan@huawei.com,
fanhenglong@huawei.com,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: Does Xen project have test suites for testing xc/xl/hypercall and so on?
Date: Mon, 10 Aug 2015 13:18:34 +0100 [thread overview]
Message-ID: <55C8969A.3060307@citrix.com> (raw)
In-Reply-To: <55C470B1.9000704@huawei.com>
On 07/08/15 09:47, Jinjian (Ken) wrote:
> Hi all,
> I'm looking into xen's test suites now, and encounter some problems.
> Does xen have unit tests that can be executed by xen contributors to
> validate their code-commits before sending a patch to xen-devel?
> In xen-4.5.1(and its upstream), there are sevral test cases in the
> 'tests' directory, but these are much like tools, rather than test
> cases at my view. For example, it obtains physical address by
> hypercall and write relevant MSR in mce-test, but it didn't tell us
> whether the address obtained was correct? and is the register written
> successfully? There seems to have no method or expected results to
> check them.
> If it was unit test, it is obviously not enough for xen. Are there
> any more test methods to ensure the accuracy and stability of xen?
There is basically nothing in the way of unit tests which I am aware
of. We rely on code review and functional testing primarily.
I have some plans to introduce some functional tests from a guests
perspective. I hope to have these ready in the 4.7 timeframe, but there
is nothing similar which I am aware of.
~Andrew
next prev parent reply other threads:[~2015-08-10 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 8:47 Does Xen project have test suites for testing xc/xl/hypercall and so on? Jinjian (Ken)
2015-08-10 12:18 ` Andrew Cooper [this message]
2015-08-10 12:30 ` Lars Kurth
2015-08-10 13:01 ` Stefano Stabellini
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=55C8969A.3060307@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=fanhenglong@huawei.com \
--cc=guoyanjuan@huawei.com \
--cc=jinjian@huawei.com \
--cc=john.liuqiming@huawei.com \
--cc=peter.huangpeng@huawei.com \
--cc=xen-devel@lists.xen.org \
/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.