From: Eric Blake <eblake@redhat.com>
To: Fam Zheng <famz@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Max Reitz" <mreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH] docs: Add docs/devel/testing.rst
Date: Mon, 29 Jan 2018 08:36:51 -0600 [thread overview]
Message-ID: <ae6cb50d-28d8-da44-e57b-6170dd60fafc@redhat.com> (raw)
In-Reply-To: <CAK1Eb9mjV4KV2N8=yOdUVeg+P0sHnqER0BUYg5kb_FjVcmzXnQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
On 01/29/2018 01:42 AM, Fam Zheng wrote:
> On Mon, Jan 29, 2018 at 2:56 PM, Thomas Huth <thuth@redhat.com> wrote:
>> On 29.01.2018 04:31, Fam Zheng wrote:
>> [...]
>>> +1. Create a new source file. For example, ``tests/test-foo.c``.
>> [...]
>>> +1. Create a new source file for the test. (More than one file can be added as
>>> + necessary.) For example, ``tests/test-foo-device.c``. 2. Write the test
>>> + code with the glib and libqtest/libqos API. See also existing tests and the
>>> + library headers for reference.
>>
>> Can you please name the examples tests/foo-test.c and
>> tests/foo-device-test.c instead? Then the binaries will be covered by
>> the wildcard in tests/.gitignore automatically. Otherwise the list in
>> that gitignore file will grow and grow... Maybe it's also worth to
>> mention the naming scheme in this doc file?
>
> Yeah, I can do it. It's just I fail to find a definitive guideline on
> test-* vs *-test for the names, and the numbers are neck-and-neck:
>
> fam@lemon:~/work/qemu [master]$ ls tests/*test.c | wc -l
> 67
> fam@lemon:~/work/qemu [master]$ ls tests/test-*.c | wc -l
> 68
I'm all for a mass rename to the suffix style (as it is easier to write
a gitignore suffix), if no one can provide a good reason for the naming
difference. (At one point, the difference was based on whether the test
was standalone or run as part of 'make check-qtest' - but I don't think
even that rule applies very well to the current state).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2018-01-29 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 3:31 [Qemu-devel] [PATCH] docs: Add docs/devel/testing.rst Fam Zheng
2018-01-29 3:42 ` no-reply
2018-01-29 6:09 ` Fam Zheng
2018-01-29 6:56 ` Thomas Huth
2018-01-29 7:42 ` Fam Zheng
2018-01-29 14:36 ` Eric Blake [this message]
2018-01-29 15:16 ` Thomas Huth
2018-01-29 10:36 ` Alex Bennée
2018-01-31 3:20 ` Fam Zheng
2018-01-29 11:04 ` Stefan Hajnoczi
2018-01-29 14:38 ` Eric Blake
2018-01-29 16:10 ` Stefan Hajnoczi
2018-01-29 16:27 ` Eric Blake
2018-01-31 3:18 ` Fam Zheng
2018-01-29 14:51 ` Eric Blake
2018-01-31 3:15 ` Fam Zheng
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=ae6cb50d-28d8-da44-e57b-6170dd60fafc@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@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 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).