From: Eric Blake <eblake@redhat.com>
To: Leandro Dorileo <l@dorileo.org>, qemu-devel@nongnu.org
Cc: "Wenchao Xia" <wenchaoqemu@gmail.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Chunyan Liu" <cyliu@suse.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2] QemuOpt: add unit tests
Date: Fri, 21 Mar 2014 08:37:40 -0600 [thread overview]
Message-ID: <532C4EB4.6030506@redhat.com> (raw)
In-Reply-To: <1395097833-3021-1-git-send-email-l@dorileo.org>
[-- Attachment #1: Type: text/plain, Size: 2503 bytes --]
On 03/17/2014 05:10 PM, Leandro Dorileo wrote:
> Cover basic aspects and API usage for QemuOpt. The current implementation
> covers the API's planned to be changed by Chunyan Liu in his QEMUOptionParameter
> replacement/cleanup job.
>
> Other APIs should be covered in future improvements.
>
> Signed-off-by: Leandro Dorileo <l@dorileo.org>
Right here is where you should stick a --- marker.
>
> Changes:
> v2:
> + fixed comments;
> + make use of g_assert_cmpstr();
> + use error_abort instead of a local_err for qemu_opts_absorb_qdict();
> + asserts on QemuOptsList (empty and list name);
> + added test_qemu_opt_unset();
> + asserts on qemu_opt_*_set() return;
> + added test_qemu_opts_reset();
> + added test_qemu_opts_set();
> ---
It's okay to have a duplicate one; but the main point is that the v2
changelog is useful to reviewers but not to the git log; and anything
after the --- marker gets omitted by 'git am' when a maintainer accepts
your patch into their pull request.
> tests/Makefile | 3 +
> tests/test-qemu-opts.c | 455 +++++++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 458 insertions(+)
> create mode 100644 tests/test-qemu-opts.c
>
> +static void test_qemu_find_opts(void)
> +{
> + QemuOptsList *list;
> +
> + register_opts();
> +
> + /* we have an "opts_list_01" option, should return it */
> + list = qemu_find_opts("opts_list_01");
> + g_assert(list != NULL);
> + g_assert_cmpstr(list->name, ==, "opts_list_01");
> +}
> +
> +static void test_qemu_opts_create(void)
> +{
> + QemuOptsList *list;
> + QemuOpts *opts;
> +
> + register_opts();
> +
> + list = qemu_find_opts("opts_list_01");
> + g_assert(list != NULL);
> + g_assert(QTAILQ_EMPTY(&list->head));
> + g_assert_cmpstr(list->name, ==, "opts_list_01");
This test starts as a duplicate of test_qemu_find_opts; I guess that's
okay (having both tests means a bit more insight into what broke if one
fails but the other passes).
> +
> +static void test_qemu_opt_unset(void)
> +{
> + QemuOpts *opts;
> + const char *value;
> + int ret;
> +
> + /* dinamically initialized (parsed) opts */
s/dinamically/dynamically/
That's trivially fixable, so feel free to add:
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-03-21 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 23:10 [Qemu-devel] [PATCH v2] QemuOpt: add unit tests Leandro Dorileo
2014-03-21 14:37 ` Eric Blake [this message]
2014-03-21 14:56 ` Leandro Dorileo
2014-03-21 15:30 ` Laszlo Ersek
2014-03-21 16:37 ` Leandro Dorileo
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=532C4EB4.6030506@redhat.com \
--to=eblake@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=cyliu@suse.com \
--cc=l@dorileo.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wenchaoqemu@gmail.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.