From: Cleber Rosa <crosa@redhat.com>
To: qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Max Reitz" <mreitz@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Caio Carrara" <ccarrara@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: [Qemu-devel] [RFC PATCH 0/2] Acceptance tests for qemu-img
Date: Fri, 9 Nov 2018 17:12:11 -0500 [thread overview]
Message-ID: <20181109221213.7310-1-crosa@redhat.com> (raw)
The initial goal of this RFC is to get feedback on tests not specific
to the QEMU main binary, but specific to other components such as
qemu-img.
For this experiment, a small issue with the zero and negative number
of I/O operations given to the bench command was chosen.
Cleber Rosa (2):
Acceptance Tests: add QemuImgTest base class
qemu-img: consider a zero number of I/O requests an invalid count
qemu-img.c | 8 ++---
tests/acceptance/avocado_qemu/__init__.py | 20 ++++++++++++
tests/acceptance/qemu_img_bench.py | 34 ++++++++++++++++++++
tests/acceptance/qemu_img_bench.py.data/img | 1 +
tests/data/images/empty/raw | Bin 0 -> 1024 bytes
5 files changed, 59 insertions(+), 4 deletions(-)
create mode 100644 tests/acceptance/qemu_img_bench.py
create mode 120000 tests/acceptance/qemu_img_bench.py.data/img
create mode 100644 tests/data/images/empty/raw
--
2.19.1
next reply other threads:[~2018-11-09 22:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 22:12 Cleber Rosa [this message]
2018-11-09 22:12 ` [Qemu-devel] [RFC PATCH 1/2] Acceptance Tests: add QemuImgTest base class Cleber Rosa
2018-11-09 22:12 ` [Qemu-devel] [RFC PATCH 2/2] qemu-img: consider a zero number of I/O requests an invalid count Cleber Rosa
2018-11-12 14:38 ` Philippe Mathieu-Daudé
2018-11-12 15:04 ` Cleber Rosa
2018-11-12 10:49 ` [Qemu-devel] [RFC PATCH 0/2] Acceptance tests for qemu-img Kevin Wolf
2018-11-12 14:59 ` Cleber Rosa
2018-11-12 15:11 ` Daniel P. Berrangé
2018-11-12 16:00 ` Kevin Wolf
2018-11-12 17:36 ` Cleber Rosa
2018-11-13 9:39 ` Markus Armbruster
2018-11-13 13:50 ` Daniel P. Berrangé
2018-11-13 14:41 ` Cleber Rosa
2018-11-13 12:18 ` Kevin Wolf
2018-11-13 13:26 ` Eduardo Habkost
2018-11-13 13:51 ` Kevin Wolf
2018-11-13 13:56 ` Eduardo Habkost
2018-11-13 14:20 ` Cleber Rosa
2018-11-13 14:32 ` Eduardo Habkost
2018-11-13 14:43 ` Cleber Rosa
2018-11-13 14:51 ` Eduardo Habkost
2018-11-13 14:15 ` Cleber Rosa
2018-11-13 15:38 ` Kevin Wolf
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=20181109221213.7310-1-crosa@redhat.com \
--to=crosa@redhat.com \
--cc=ccarrara@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@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 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.