From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Thomas Huth <thuth@redhat.com>, Willian Rampazzo <wrampazz@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Niek Linnenbank" <nieklinnenbank@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
"Michael Rolnik" <mrolnik@gmail.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [RFC 1/1] acceptance tests: rename acceptance to system
Date: Fri, 21 May 2021 14:49:24 +0200 [thread overview]
Message-ID: <0b970add-1804-f841-819d-e77a64d616e8@redhat.com> (raw)
In-Reply-To: <82f5ed3f-3047-bfa3-c7b2-d91300f393f8@redhat.com>
On 5/21/21 2:42 PM, Thomas Huth wrote:
> On 21/05/2021 14.28, Willian Rampazzo wrote:
>> On Fri, May 21, 2021 at 4:16 AM Thomas Huth <thuth@redhat.com> wrote:
> [...]
>>> Alternatively, what about renaming the "acceptance" tests to
>>> "validation"
>>> instead? That word does not have a duplicated definition in the
>>> context of
>>> QEMU yet, so I think it would be less confusing.
>>
>> While at the beginning of your reply, I started thinking if
>> "validation" would cause less confusion for the QEMU project. Although
>> validation testing is a broader concept inside the Verification &
>> Validation process, encompassing unit testing, functional testing,
>> integration testing, system testing, and acceptance testing, it may be
>> an option for the QEMU project.
>>
>> While system testing would be the correct terminology to use, if it
>> causes more confusion, using a less strict terminology, like
>> validation testing, is valid, in my opinion.
>
> <semi-homorous-friday-bikeshedding>
> Or we could come up with a new, artificial name instead (like "qtests").
> It certainly need a "q" in the name. For example what about:
>
> - avoqado
+1 for 'make check-avoqado' :)
next prev parent reply other threads:[~2021-05-21 12:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 19:53 [RFC 0/1] acceptance tests: rename acceptance to system Willian Rampazzo
2021-05-20 19:53 ` [RFC 1/1] " Willian Rampazzo
2021-05-20 20:28 ` Philippe Mathieu-Daudé
2021-05-21 7:16 ` Thomas Huth
2021-05-21 12:28 ` Willian Rampazzo
2021-05-21 12:31 ` Philippe Mathieu-Daudé
2021-05-21 13:03 ` Alex Bennée
2021-05-21 14:18 ` Philippe Mathieu-Daudé
2021-05-21 14:29 ` Peter Maydell
2021-05-21 14:53 ` Willian Rampazzo
2021-05-21 15:12 ` Willian Rampazzo
2021-05-21 15:22 ` Peter Maydell
2021-05-21 15:34 ` Willian Rampazzo
2021-05-21 17:14 ` Thomas Huth
2021-05-21 17:46 ` Philippe Mathieu-Daudé
2021-05-21 17:49 ` Willian Rampazzo
2021-05-21 14:43 ` Alex Bennée
2021-05-21 12:42 ` Thomas Huth
2021-05-21 12:49 ` Philippe Mathieu-Daudé [this message]
2021-05-21 13:05 ` Alex Bennée
2021-05-21 12:09 ` Willian Rampazzo
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=0b970add-1804-f841-819d-e77a64d616e8@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=crosa@redhat.com \
--cc=mrolnik@gmail.com \
--cc=nieklinnenbank@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).