aboutsummaryrefslogtreecommitdiffstats
path: root/docs/testing/user/configguide/configguide.rst
diff options
context:
space:
mode:
authorMorgan Richomme <morgan.richomme@orange.com>2017-03-27 06:41:33 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-03-27 06:41:33 +0000
commitdcf1e078e3ffde4ed57c0cc6da05534ab419ca22 (patch)
treedb927ca60fbd399038880c9c398544aa3d75da7f /docs/testing/user/configguide/configguide.rst
parent18745da8f335fe3049ffdd5acdafb5848981a1c9 (diff)
parent19f9f2a99641cca98b896aa975a2182c43ba7f97 (diff)
Merge "Update documentation for Danube"
Diffstat (limited to 'docs/testing/user/configguide/configguide.rst')
-rw-r--r--docs/testing/user/configguide/configguide.rst13
1 files changed, 6 insertions, 7 deletions
diff --git a/docs/testing/user/configguide/configguide.rst b/docs/testing/user/configguide/configguide.rst
index 56a414d3..494ad7e6 100644
--- a/docs/testing/user/configguide/configguide.rst
+++ b/docs/testing/user/configguide/configguide.rst
@@ -1,5 +1,5 @@
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
+.. SPDX-License-Identifier: CC-BY-4.0
Pulling the Docker image
@@ -16,8 +16,8 @@ created automatically by the CI mechanisms, and you must ensure you
pull an image with the **correct tag** to match the OPNFV software
release installed in your environment. All available tagged images can
be seen from location [FunctestDockerTags_]. For example, when running
-on the first official release of the OPNFV Colorado system platform,
-tag "colorado.1.0" is needed. Pulling other tags might cause some
+on the first official release of the OPNFV Danube system platform,
+tag "danube.1.0" is needed. Pulling other tags might cause some
problems while running the tests.
Docker images pulled without a tag specifier bear the implicitly
assigned label "latest". If you need to specifically pull the latest
@@ -201,7 +201,7 @@ when performing manual test scenarios::
tests are activated under Jenkins CI control.
It enables the correlation of test results,
which
- are independently pushed to the results datbase
+ are independently pushed to the results database
from different Jenkins jobs.
DO NOT USE THIS OPTION IN MANUAL TEST SCENARIOS.
<DebugTraceValue> = "true" or "false"
@@ -444,8 +444,7 @@ We may distinguish several directories, the first level has 4 directories:
* **docker**: This directory includes the needed files and tools to
build the Funtest Docker image.
* **docs**: This directory includes documentation: Release Notes,
- User Guide, Configuration Guide and Developer Guide. Test results
- are also located in a sub--directory called 'results'.
+ User Guide, Configuration Guide and Developer Guide.
* **functest**: This directory contains all the code needed to run
functest internal cases and OPNFV onboarded feature or VNF test cases.
@@ -592,7 +591,7 @@ prompt::
- here = "false"
NOTE: In Jenkins CI runs, an additional item "BUILD TAG"
- would also be listed. The valaue is set by Jenkins CI.
+ would also be listed. The value is set by Jenkins CI.
Finally, the **functest** CLI has a **--help** options: