path: root/docs/testing
diff options
authorxudan <>2019-04-11 02:52:04 -0400
committerDan Xu <>2019-04-12 02:53:31 +0000
commitf170bf4205fd75db96b84a685b931904f4dbab93 (patch)
tree4b9302734716e4c38458e9690bfdbb6f4dff05db /docs/testing
parent06a0a8f2bd8ee7ce7db154c54301ec986b93b89f (diff)
Update user guide
Change-Id: I595975d13630c81c5d15ac0051225143d0394ba4 Signed-off-by: xudan <>
Diffstat (limited to 'docs/testing')
2 files changed, 29 insertions, 7 deletions
diff --git a/docs/testing/user/userguide/testing_guide.rst b/docs/testing/user/userguide/testing_guide.rst
index c6911f6..828813c 100644
--- a/docs/testing/user/userguide/testing_guide.rst
+++ b/docs/testing/user/userguide/testing_guide.rst
@@ -2,12 +2,12 @@
.. (c) OPNFV, Huawei Technologies Co.,Ltd and others.
Conducting OVP Testing with Dovetail
The Dovetail testing framework for OVP consists of two major parts: the testing client which
executes all test cases in a lab (vendor self-testing or a third party lab),
@@ -749,7 +749,7 @@ until they are ready to submit results for peer community review.
* Web Site URL
- *
+ *
* Sign In / Sign Up Links
diff --git a/docs/testing/user/userguide/vnf_test_guide.rst b/docs/testing/user/userguide/vnf_test_guide.rst
index f37858c..1e269fb 100644
--- a/docs/testing/user/userguide/vnf_test_guide.rst
+++ b/docs/testing/user/userguide/vnf_test_guide.rst
@@ -69,7 +69,10 @@ The VNF package to be tested should be copied to the container 'refrepo'.
Run Tests with Dovetail
+Setting up Configuration Files
For convenience and as a convention, we will create a home directory for storing
all Dovetail related config files and results files:
@@ -92,7 +95,9 @@ test results are going to be saved:
$ chmod 777 ${DOVETAIL_HOME}/results
-There should be a file `` inside this directory to provide some info.
+There should be a file `` inside ``pre_config`` directory to provide
+some info needed by test cases.
For TOSCA based VNFs, it should look like this:
.. code-block:: bash
@@ -115,6 +120,9 @@ Configuration file `` should look like this for HEAT based VNFs:
export VNF_ARCHIVE_NAME="vnf_archive_name"
+Starting Dovetail Docker
Use the command below to create a Dovetail container and get access to its shell:
.. code-block:: bash
@@ -133,16 +141,26 @@ the configuration files and write result files into DOVETAIL_HOME on the Test
Host. The user should be within the Dovetail container shell, once the command
above is executed. In order to run ONAP VNF tests 'latest' <tag> must be used.
+Running OVP Test Suites
Run VNF tests with the following command:
.. code-block:: bash
- $ dovetail run --testsuite <suite name> -d
+ $ dovetail run --testsuite <suite name> -d -r
For TOSCA based VNFs, `<suite name>` is `onap.tosca.2019.04` and for
HEAT based ones, it is `onap.heat.2019.04`.
+When test execution is complete, a tar file with all result and log files is
+written in ``$DOVETAIL_HOME`` on the Test Host. An example filename is
+``${DOVETAIL_HOME}/logs_20180105_0858.tar.gz``. The file is named using a
+timestamp that follows the convention ‘YearMonthDay-HourMinute’. In this case,
+it was generated at 08:58 on January 5th, 2018. This tar file is used for
+uploading the logs to `OVP VNF portal`_.
NOTE: If Dovetail run fails when testing `onap-vtp.validate.csar`, then follow the
below guidelines to run the test again.
@@ -154,3 +172,7 @@ below guidelines to run the test again.
$ cd $OPEN_CLI_HOME/bin
$ ./
$ #Exit docker by running CTRL+p+q
+.. References
+.. _`OVP VNF portal`: