All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wenchao Xia <wenchaoqemu@gmail.com>
To: Eric Blake <eblake@redhat.com>
Cc: mdroth@linux.vnet.ibm.com, lcapitulino@redhat.com,
	qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH V3 4/5] test: add test cases for qapi event
Date: Mon, 24 Mar 2014 09:01:08 +0800	[thread overview]
Message-ID: <532F83D4.4020700@gmail.com> (raw)
In-Reply-To: <532B869C.6020506@redhat.com>

于 2014/3/21 8:23, Eric Blake 写道:
> On 03/18/2014 11:16 PM, Wenchao Xia wrote:
>> These cases will verify whether the expected qdict is built.
>>
>> Signed-off-by: Wenchao Xia<wenchaoqemu@gmail.com>
>> ---
>>   tests/Makefile                          |   14 ++-
>>   tests/qapi-schema/qapi-schema-test.json |   12 ++
>>   tests/qapi-schema/qapi-schema-test.out  |   10 +-
>>   tests/test-qmp-event.c                  |  258 +++++++++++++++++++++++++++++++
>>   4 files changed, 289 insertions(+), 5 deletions(-)
>>   create mode 100644 tests/test-qmp-event.c
>>
>
>> +++ b/tests/test-qmp-event.c
>> @@ -0,0 +1,258 @@
>> +/*
>> + * qapi event unit-tests.
>> + *
>> + * Authors:
>> + *  Wenchao Xia<wenchaoqemu@gmail.com>
>> + *
>> + * This work is licensed under the terms of the GNU LGPL, version 2.1 or later.
>> + * See the COPYING.LIB file in the top-level directory.
>> + *
> Missing "Copyright"
>
>> +    case QTYPE_QINT:
>> +        d->result = (qint_get_int(qobject_to_qint(obj1)) ==
>> +                     qint_get_int(qobject_to_qint(obj2)));
>> +        return;
>> +    case QTYPE_QSTRING:
>> +        if (!g_strcmp0(qstring_get_str(qobject_to_qstring(obj1)),
>> +                       qstring_get_str(qobject_to_qstring(obj2)))) {
>> +            d->result = true;
>> +        } else {
>> +            d->result = false;
>> +        }
> Could also be written without 'if':
>    d->result = g_strcmp0(...) == 0;
>
>> +    obj = qdict_get(t, "seconds");
>> +    g_assert(obj&&  qobject_type(obj) == QTYPE_QINT);
>> +    obj = qdict_get(t, "microseconds");
>> +    g_assert(obj&&  qobject_type(obj) == QTYPE_QINT);
> Might be worth asserting that microseconds is within the range
> [0,999999] (or -1 if seconds is -1)
>
   will add those test.

  reply	other threads:[~2014-03-24  1:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19  5:16 [Qemu-devel] [RFC PATCH V3 0/5] add direct support of event in qapi schema Wenchao Xia
2014-03-19  5:16 ` [Qemu-devel] [RFC PATCH V3 1/5] os-posix: include sys/time.h Wenchao Xia
2014-03-19  5:16 ` [Qemu-devel] [RFC PATCH V3 2/5] qapi: add event helper functions Wenchao Xia
2014-03-20 22:53   ` Eric Blake
2014-03-24  0:53     ` Wenchao Xia
2014-03-24 13:11       ` Eric Blake
2014-03-19  5:16 ` [Qemu-devel] [RFC PATCH V3 3/5] qapi script: add event support Wenchao Xia
2014-03-20 23:06   ` Eric Blake
2014-03-24  0:59     ` Wenchao Xia
2014-03-19  5:16 ` [Qemu-devel] [RFC PATCH V3 4/5] test: add test cases for qapi event Wenchao Xia
2014-03-21  0:23   ` Eric Blake
2014-03-24  1:01     ` Wenchao Xia [this message]
2014-03-19  5:16 ` [Qemu-devel] [RFC PATCH V3 5/5] qapi event: convert RTC_CHANGE Wenchao Xia
2014-03-21  0:25   ` Eric Blake

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=532F83D4.4020700@gmail.com \
    --to=wenchaoqemu@gmail.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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 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.