From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, drjones@redhat.com
Subject: [kvm-unit-tests v2 2/2] README: Add intro about the configuration file
Date: Mon, 20 Jan 2020 16:43:10 -0300 [thread overview]
Message-ID: <20200120194310.3942-3-wainersm@redhat.com> (raw)
In-Reply-To: <20200120194310.3942-1-wainersm@redhat.com>
The 'Guarding unsafe tests' section mention the unittests.cfg
file which was never introduced before. In this change
it was added a section with a few words about the tests
configuration file (unittests.cfg).
Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
---
README.md | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/README.md b/README.md
index 367c92a..763759e 100644
--- a/README.md
+++ b/README.md
@@ -52,6 +52,17 @@ ACCEL=name environment variable:
ACCEL=kvm ./x86-run ./x86/msr.flat
+# Tests configuration file
+
+The test case may need specific runtime configurations, for
+example, extra QEMU parameters and time to execute limited, the
+runner script reads those information from a configuration file found
+at ./ARCH/unittests.cfg.
+
+The configuration file also contain the groups (if any) each test belong
+to. So that a given group can be executed by specifying its name in the
+runner's -g option.
+
# Unit test inputs
Unit tests use QEMU's '-append args...' parameter for command line
--
2.23.0
next prev parent reply other threads:[~2020-01-20 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 19:43 [kvm-unit-tests v2 0/2] README: Markdown fixes and improvements Wainer dos Santos Moschetta
2020-01-20 19:43 ` [kvm-unit-tests v2 1/2] README: Fix markdown formatting Wainer dos Santos Moschetta
2020-01-21 9:18 ` Andrew Jones
2020-01-21 12:20 ` Paolo Bonzini
2020-01-20 19:43 ` Wainer dos Santos Moschetta [this message]
2020-01-21 9:22 ` [kvm-unit-tests v2 2/2] README: Add intro about the configuration file Andrew Jones
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=20200120194310.3942-3-wainersm@redhat.com \
--to=wainersm@redhat.com \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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