From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: eesposit@redhat.com, vsementsov@virtuozzo.com, mreitz@redhat.com
Subject: [PATCH v4 0/5] qemu-iotests: quality of life improvements
Date: Mon, 3 May 2021 13:01:05 +0200 [thread overview]
Message-ID: <20210503110110.476887-1-pbonzini@redhat.com> (raw)
This series adds a few usability improvements to qemu-iotests, mostly
for Python unittest-based tests. In particular:
- the output of the unittest framework is not buffered, which makes it
easier to follow the "-d" output of the tests
- arguments can be passed to Python unittests scripts, for example
to run only a subset of the test cases (patches 1-2)
- it is possible to do "./check -- ../../../tests/qemu-iotests/055 args..."
and specify arbitrary arguments to be passed to a single test script.
This is especially useful together with the previous feature and eases
the debugging of Python tests.
Paolo
v3->v4: output of Python tests regenerated when needed
Paolo Bonzini (5):
qemu-iotests: do not buffer the test output
qemu-iotests: allow passing unittest.main arguments to the test
scripts
qemu-iotests: move command line and environment handling from
TestRunner to TestEnv
qemu-iotests: let "check" spawn an arbitrary test command
qemu-iotests: fix case of SOCK_DIR already in the environment
tests/qemu-iotests/240.out | 8 ++--
tests/qemu-iotests/245.out | 8 ++--
tests/qemu-iotests/295.out | 6 +--
tests/qemu-iotests/296.out | 8 ++--
tests/qemu-iotests/check | 19 +++++++-
tests/qemu-iotests/iotests.py | 80 +++++++++++++++++++-------------
tests/qemu-iotests/testenv.py | 22 +++++++--
tests/qemu-iotests/testrunner.py | 15 +-----
8 files changed, 101 insertions(+), 65 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-03 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 11:01 Paolo Bonzini [this message]
2021-05-03 11:01 ` [PATCH v4 1/5] qemu-iotests: do not buffer the test output Paolo Bonzini
2021-05-03 11:01 ` [PATCH v4 2/5] qemu-iotests: allow passing unittest.main arguments to the test scripts Paolo Bonzini
2021-05-03 11:01 ` [PATCH v4 3/5] qemu-iotests: move command line and environment handling from TestRunner to TestEnv Paolo Bonzini
2021-05-03 11:01 ` [PATCH v4 4/5] qemu-iotests: let "check" spawn an arbitrary test command Paolo Bonzini
2021-05-03 11:01 ` [PATCH v4 5/5] qemu-iotests: fix case of SOCK_DIR already in the environment Paolo Bonzini
2021-05-03 12:23 ` [PATCH v4 0/5] qemu-iotests: quality of life improvements Max Reitz
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=20210503110110.476887-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=eesposit@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).