From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PATCH 0/2] simplify tests/qtest/meson.build and update docs
Date: Wed, 7 Oct 2020 04:03:10 -0400 [thread overview]
Message-ID: <20201007080312.566464-1-pbonzini@redhat.com> (raw)
The instructions for adding new unit tests were not in
build-system.rst and therefore I missed them in the Meson
conversion. Patch 2 updates them; before that, however,
patch 1 applies the same trick to qtests that was used to
simplify the unit tests conversion.
Paolo Bonzini (2):
qtest: unify extra_qtest_srcs and extra_qtest_deps
docs/devel: update instruction on how to add new unit tests
docs/devel/qtest.rst | 30 +++++++++++++++-------
docs/devel/testing.rst | 19 +++++++-------
tests/qtest/meson.build | 55 +++++++++++++++++++----------------------
3 files changed, 57 insertions(+), 47 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-07 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 8:03 Paolo Bonzini [this message]
2020-10-07 8:03 ` [PATCH 1/2] qtest: unify extra_qtest_srcs and extra_qtest_deps Paolo Bonzini
2020-10-07 8:03 ` [PATCH 2/2] docs/devel: update instruction on how to add new unit tests Paolo Bonzini
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=20201007080312.566464-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).