From: Cleber Rosa <crosa@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Fam Zheng" <famz@redhat.com>, "Amador Pahim" <amador@pahim.org>
Subject: [Qemu-devel] [PATCH v3 0/5] Acceptance/functional tests
Date: Tue, 29 May 2018 15:37:25 -0400 [thread overview]
Message-ID: <20180529193730.9204-1-crosa@redhat.com> (raw)
TL;DR
=====
Another version, with a minimalist approach, to the acceptance tests
infrastructure for QEMU, based on the Avocado Testing Framework.
Background
==========
The previous version, still considered an RFC, was sent to the list by
Eduardo[1] was based on the work held in Amador's branch[2]. After
reviewing in under a different light, including the experiences
done and reported by Philippe[3], it was clear to me that a different
approach would be better.
Differences from previous versions
==================================
The main difference is that this series include only the minimal
changes deemed necessary to have a starting point. I like to think
that it's better connected to the QEMU community and project needs,
and will hopefully allow for a more organic growth.
Since this version has less features than the previous versions,
provided it's accepted, these are the next probable development tasks:
* Provide a simple variants mechanism to allow the same tests to be
run under different targets, machine models and devices (present on
the previous versions as a "YAML to Mux" file with architecture
definitions)
* Implement QEMUMachine migration support (present on the previous
version in the "avocado_qemu.test._VM" class)
* Implement Guest OS image selection and download (mostly an Avocado
feature, paired with a parameter convention and cloud-init support
code)
* Implement interactive support for Guest OS sessions (present on
the previous versions, supported by the aexpect Python module)
* Move the Python modules that are used on tests to a more proper
"module" organization. This should allow for a proper place
to hold tests for the Python modules themselves.
Even though this version shares very little (if any) code with the
previous versions, the following is a list of noteworthy changes:
* Tests directory is now "tests/acceptance" (was "tests/avocado")
* Base test class is now "avocado_qemu.Test" (was
"avocado_qemu.test.QemuTest")
* Base test class is now hosted in "avocado_qemu/__init__.py" (was
"avocado_qemu/test.py")
* Direct use of "qemu.QEMUMachine", that is, the
avocado_qemu.test._VM class is gone
* avocado_qemu.Test won't search for QEMU binaries on $PATH. To use
QEMU binary on a custom system location it's necessary to use the
"qemu_bin" parameter
* Example test in README.rst is distributed as a real test
("test_version.py")
* A new "Linux boot console" test, loosely modeled after Phillipe's
use case
Changes
=======
>From v2
-------
* Renamed acceptance test files, dropping "test_" prefix.
* Dropped "scripts/test_qemu.py" until we have a proper Python module
location on which to put their own tests.
>From v1
-------
* Moved documentation to docs/devel/testing.rst
* Changed code markers from "::" to ".. code::" in the documentation
for consistency
* Added copyright notices
* Removed useless "qemu_bin=None" attribution on avocado_qemu.Test.setUp()
* Removed reference about setting arguments, instead of appending them,
on "Acceptance tests: add quick VNC tests" commit message
* Fixed typo (s/inteligence/intelligence/) on "scripts/qemu.py:
introduce set_console() method" commit message
* Removed useless "return" in add_args()
Commit summary
==============
Cleber Rosa (5):
Add functional/acceptance tests infrastructure
scripts/qemu.py: allow adding to the list of extra arguments
Acceptance tests: add quick VNC tests
scripts/qemu.py: introduce set_console() method
Acceptance tests: add Linux kernel boot and console checking test
docs/devel/testing.rst | 153 +++++++++++++++++++++++++++++
scripts/qemu.py | 103 ++++++++++++++++++-
tests/acceptance/README.rst | 10 ++
tests/acceptance/avocado_qemu/__init__.py | 54 ++++++++++
tests/acceptance/boot_linux_console.py | 47 +++++++++
tests/acceptance/version.py | 24 +++++
tests/acceptance/vnc.py | 60 +++++++++++
7 files changed, 450 insertions(+), 1 deletion(-)
create mode 100644 tests/acceptance/README.rst
create mode 100644 tests/acceptance/avocado_qemu/__init__.py
create mode 100644 tests/acceptance/boot_linux_console.py
create mode 100644 tests/acceptance/version.py
create mode 100644 tests/acceptance/vnc.py
---
[1] https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg03443.html
[2] https://github.com/apahim/qemu/commits/avocado_qemu
[3] https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg03076.html
next reply other threads:[~2018-05-29 19:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 19:37 Cleber Rosa [this message]
2018-05-29 19:37 ` [Qemu-devel] [PATCH v3 1/5] Add functional/acceptance tests infrastructure Cleber Rosa
2018-05-30 12:54 ` Stefan Hajnoczi
2018-05-30 18:15 ` Cleber Rosa
2018-05-29 19:37 ` [Qemu-devel] [PATCH v3 2/5] scripts/qemu.py: allow adding to the list of extra arguments Cleber Rosa
2018-05-30 12:54 ` Stefan Hajnoczi
2018-05-29 19:37 ` [Qemu-devel] [PATCH v3 3/5] Acceptance tests: add quick VNC tests Cleber Rosa
2018-05-30 12:57 ` Stefan Hajnoczi
2018-05-30 13:04 ` Fam Zheng
2018-05-30 16:29 ` Eduardo Habkost
2018-05-30 18:00 ` Cleber Rosa
2018-05-30 20:00 ` Eduardo Habkost
2018-05-30 21:03 ` Cleber Rosa
2018-05-30 21:31 ` Eduardo Habkost
2018-05-30 22:28 ` Cleber Rosa
2018-05-30 12:57 ` Stefan Hajnoczi
2018-05-29 19:37 ` [Qemu-devel] [PATCH v3 4/5] scripts/qemu.py: introduce set_console() method Cleber Rosa
2018-05-30 19:17 ` Stefan Hajnoczi
2018-05-29 19:37 ` [Qemu-devel] [PATCH v3 5/5] Acceptance tests: add Linux kernel boot and console checking test Cleber Rosa
2018-05-30 19:20 ` Stefan Hajnoczi
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=20180529193730.9204-1-crosa@redhat.com \
--to=crosa@redhat.com \
--cc=amador@pahim.org \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).