From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Willian Rampazzo <willianr@redhat.com>,
qemu-devel@nongnu.org, QEMU Trivial <qemu-trivial@nongnu.org>
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>
Subject: Re: [PATCH 2/2] docs: add definitions of terms for CI/testing
Date: Mon, 30 Aug 2021 15:34:14 +0200 [thread overview]
Message-ID: <66629452-44dd-865e-1912-c6d89fbf202a@redhat.com> (raw)
In-Reply-To: <20210820210946.291335-3-willianr@redhat.com>
On 8/20/21 11:09 PM, Willian Rampazzo wrote:
> To understand the current state of QEMU CI/testing and have a base to
> discuss the plans for the future, it is important to define some usual
> terms. This patch defines the terms for "Automated tests", "Unit
> testing", "Functional testing", "System testing", "Flaky tests",
> "Gating", and "Continuous Integration".
>
> The first patch was borrowed from
> 20210812180403.4129067-1-berrange@redhat.com.
^ These 2 lines belong to the cover and are irrelevant in this context.
Cc'ing qemu-trivial@ otherwise (patch reviewed).
> Signed-off-by: Willian Rampazzo <willianr@redhat.com>
> ---
> docs/devel/ci-definitions.rst | 121 ++++++++++++++++++++++++++++++++++
> docs/devel/ci.rst | 1 +
> 2 files changed, 122 insertions(+)
> create mode 100644 docs/devel/ci-definitions.rst
prev parent reply other threads:[~2021-08-30 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 21:09 [PATCH 0/2] docs: add definitions of terms for CI/testing Willian Rampazzo
2021-08-20 21:09 ` [PATCH 1/2] docs: split the CI docs into two files Willian Rampazzo
2021-08-20 21:09 ` [PATCH 2/2] docs: add definitions of terms for CI/testing Willian Rampazzo
2021-08-20 22:54 ` Philippe Mathieu-Daudé
2021-08-30 13:34 ` Philippe Mathieu-Daudé [this message]
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=66629452-44dd-865e-1912-c6d89fbf202a@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@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 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.