aboutsummaryrefslogtreecommitdiffstats
path: root/docs/userguide
diff options
context:
space:
mode:
authorMorgan Richomme <morgan.richomme@orange.com>2016-09-05 11:44:41 +0200
committerMorgan Richomme <morgan.richomme@orange.com>2016-09-13 18:30:43 +0200
commite7e579f3f03d2bdce513e6bd17da3aecfbca8612 (patch)
tree87904dd97b81b4717f3aca3fc6a54af2847de23e /docs/userguide
parent17b720a1addfa444a6248baa9706bf20d012051b (diff)
Doc for Xreview by other test projects
Change-Id: I75da3530685b74f628fc689b2ef8908919df147e Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
Diffstat (limited to 'docs/userguide')
-rw-r--r--docs/userguide/index.rst4
-rw-r--r--docs/userguide/introduction.rst4
2 files changed, 4 insertions, 4 deletions
diff --git a/docs/userguide/index.rst b/docs/userguide/index.rst
index 6140f606..30bee8dc 100644
--- a/docs/userguide/index.rst
+++ b/docs/userguide/index.rst
@@ -16,7 +16,7 @@ The goal of this document is to describe the OPNFV Functest test cases and to
provide a procedure to execute them. In the OPNFV Colorado system release,
a Functest CLI utility is introduced for easier execution of test procedures.
-A overview presentation has been created for the first OPNFV Summit `[4]`_.
+An overview presentation has been created for the first OPNFV Summit `[4]`_.
This document is a continuation of the OPNFV Functest Configuration Guide `[1]`_.
@@ -360,7 +360,7 @@ The current work flow is as follows:
* Jenkins Build Initiated
* security_scan.py script is called, and a config file is passed to the script as
an argument.
- * The IP addresses of each NFVi node (compute / control), is gathered.
+ * The IP addresses of each NFVi node (compute / control) are gathered
* A scan profile is matched to the node type.
* The OpenSCAP application is remotely installed onto each target node gathered
on step 3, using upstream packaging (rpm and .deb).
diff --git a/docs/userguide/introduction.rst b/docs/userguide/introduction.rst
index fc8e6680..627f907f 100644
--- a/docs/userguide/introduction.rst
+++ b/docs/userguide/introduction.rst
@@ -195,14 +195,14 @@ offers a lot of potential combinations:
Most of the tests are runnable by any combination, but some tests might have
restrictions imposed by the utilized installers or due to the available
deployed features. The system uses the environment variables (INSTALLER_IP and
-DEPLOY_SCENARIO) to automatically determine the valid test cases; for each given
+DEPLOY_SCENARIO) to automatically determine the valid test cases, for each given
environment.
In the Colorado OPNFV System release a convenience Functest CLI utility is also
introduced to simplify setting up the Functest evironment, management of the
OpenStack environment (e.g. resource clean-up) and for executing tests.
The Functest CLI organised the testcase into logical Tiers, which contain in
-turn one or more testcases. The CLI allow execution of a single specified
+turn one or more testcases. The CLI allows execution of a single specified
testcase, all test cases in a specified Tier, or the special case of execution
of **ALL** testcases. The Functest CLI is introduced in more detail in the
section `Executing the functest suites`_ of this document.