From: "Alex Bennée" <alex.bennee@linaro.org>
To: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
Cc: "Zhangbo (Oscar)" <oscar.zhangbo@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"wangyan (AQ)" <wangyan44@huawei.com>
Subject: Re: [Qemu-devel] [qemu] how to test qemu?
Date: Fri, 26 Feb 2016 08:40:29 +0000 [thread overview]
Message-ID: <87twkv7tky.fsf@linaro.org> (raw)
In-Reply-To: <56CF1550.7040605@mail.uni-paderborn.de>
Bastian Koppelmann <kbastian@mail.uni-paderborn.de> writes:
> Hi,
>
> On 02/25/2016 01:24 PM, wangyan (AQ) wrote:
>>
>>
>> Hi all:
>> AFAIK, there're several ways to test qemu:
>> 1) virt-test, which is driven by autotest or avocado-vt, based on qemu-kvm
>> 2) Qtest��using instruction ��make check V=1��, which aims to do low level tests, that is to test function modules of qemu.
>>
>>
>> I've got 2 questions:
>> 1) besides the 2 test suites, are there any other automatic-test tools?
>
> From the top of my head I can only think of risu[1] which generates
> random instruction sequences. This is IIRC used to test whether TCG
> works correctly for ARM.
We run some basic system boot tests as well as RISU and LTP within our
LAVA system:
https://validation.linaro.org/dashboard/streams/anonymous/qemu-master/bundles/
We certainly could do more.
Also see [PATCH v2 00/15] tests: Introducing docker tests which extends
the testing capability under different build environments. I've still to
look at extending this with qemu-${ARCH}-static.
The automatic Travis tests are basically a simple compile test + make
check on Ubuntu 12.04 so a bit limited in coverage.
>
> Cheers,
> Bastian
>
> [1] https://github.com/stsquad/risu
https://git.linaro.org/people/peter.maydell/risu.git is the canonical
location although I still have some patches for replay/playback in my
tree to get merged.
I think the major hole is our TCG testing as although we have code in
tests/tcg it's not built as you require cross tools to build it. This
means $ARCH-on-x86 isn't as routinely tested as it should be. Obviously
the various arch maintainers have their own boot tests they run.
--
Alex Bennée
prev parent reply other threads:[~2016-02-26 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 12:24 [Qemu-devel] [qemu] how to test qemu? wangyan (AQ)
2016-02-25 14:53 ` Bastian Koppelmann
2016-02-26 8:40 ` Alex Bennée [this message]
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=87twkv7tky.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=kbastian@mail.uni-paderborn.de \
--cc=oscar.zhangbo@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=wangyan44@huawei.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.