[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [qemu] how to test qemu?
From: |
Alex Bennée |
Subject: |
Re: [Qemu-devel] [qemu] how to test qemu? |
Date: |
Fri, 26 Feb 2016 08:40:29 +0000 |
User-agent: |
mu4e 0.9.17; emacs 25.0.91.1 |
Bastian Koppelmann <address@hidden> 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