[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Functional tests (AKA Avocado-based tests)

From: Cleber Rosa
Subject: Re: [Qemu-devel] Functional tests (AKA Avocado-based tests)
Date: Mon, 5 Feb 2018 11:15:50 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

On 01/25/2018 09:11 AM, Stefan Hajnoczi wrote:
> On Wed, Jan 17, 2018 at 03:05:54AM -0500, Cleber Rosa wrote:
>> This is about how QEMU developers can get started with functional
>> tests that are built on top of the Avocado libraries (and meant to be
>> run with the Avocado test runner).
> Here is my guess at where this fits into QEMU's testing landscape:
> Avocado can help us write a new kind of test - functional (acceptance)
> tests - that run full-blown guest operating systems, invoke shell
> commands inside guests, and also use QMP.  Avocado can probably test
> guest OS installation and boot.

That is the main goal indeed.  Then at the same time, tests that won't
"run full-brown guest operating systems" should also be easy to
write[1].  For instance, I gave myself a few minutes, literally, to
prove this point and wrote a few VNC related tests[2].

> There is some overlap with what exists in tests/ today, but I guess it
> won't replace check (unit tests), qtests, or qemu-iotests.

There's no *need* whatsoever to replace anything.  People may see value
in using the Avocado test runner to run other tests at some point, but
that's completely unrelated to your original question and our goal.

> Is this how you envision Avocado usage in QEMU?
> Stefan

In short, yes.  The long answer has already been given above.

- Cleber.

[1] - As opposed to say, Avocado-VT, where a lot of pre/post processing,
including guest operating system images, will usually happen by default.

[2] -

Cleber Rosa
[ Sr Software Engineer - Virtualization Team - Red Hat ]
[ Avocado Test Framework - avocado-framework.github.io ]
[  7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3  ]

reply via email to

[Prev in Thread] Current Thread [Next in Thread]