Add testsuite cvp.0.8.0 for Beta tests

1. Now there is a testsuite proposed_tests for beta tests which may
   cause some confusions.
2. Copy all test cases to testsuite cvp.0.8.0 for beta testers to use.
3. Update userguide with testsuite cvp.0.8.0

JIRA: DOVETAIL-528

Change-Id: I35bc7dee6e07a9125a4c1991b0049f6e2d705cc5
Signed-off-by: xudan <xudan16@huawei.com>

1 files changed, 16 insertions, 11 deletions

diff --git a/docs/testing/user/userguide/testing_guide.rst b/docs/testing/user/userguide/testing_guide.rst
index 88c5eecc..42a9ad7f 100644
--- a/docs/testing/user/userguide/testing_guide.rst
+++ b/docs/testing/user/userguide/testing_guide.rst
@@ -397,7 +397,7 @@ Now you should be in the Dovetail container's prompt and ready to execute
 test suites.
 
 The Dovetail client CLI allows the tester to specify which test suite to run.
-You can refer to :ref:`cli-reference`.
+You can refer to :ref:`cli-reference`
 for the details of the CLI.
 By default the results are stored in a local file ``$DOVETAIL_HOME/results``.
 
@@ -407,12 +407,18 @@ By default the results are stored in a local file ``$DOVETAIL_HOME/results``.
 
 Multiple test suites may be available. For the purpose of running
 CVP test suite, the test suite name follows the following format,
-``CVP_<major>_<minor>_<patch>``
-For example, CVP_1_0_0.
+``cvp.<major>.<minor>.<patch>``.
+The latest and default test suite is cvp.0.8.0.
 
 .. code-block:: bash
 
-   $ dovetail run --testsuite CVP_1_0_0
+   $ dovetail run
+
+This command is equal to
+
+.. code-block:: bash
+
+   $ dovetail run --testsuite cvp.0.8.0
 
 If you are not running the entire test suite, you can choose to run an
 individual test area instead. The test area can be a single test area or
@@ -421,30 +427,29 @@ and "ha". The optional test areas are "ipv6", "sdnvpn" and "tempest".
 
 .. code-block:: bash
 
-   $ dovetail run --testsuite CVP_1_0_0 --testarea mandatory
+   $ dovetail run --testarea mandatory
 
 You need to push the results to local DB if you want to store the results
 or report the results to CVP.
 
 .. code-block:: bash
 
-   $ dovetail run --testsuite CVP_1_0_0 --report http://<test_host_ip>:<testapi_port>/api/v1/results
+   $ dovetail run --report http://<test_host_ip>:<testapi_port>/api/v1/results
 
 If the Test Host is offline, ``--offline`` should be added to support running with
 local resources.
 
 .. code-block:: bash
 
-   $ dovetail run --testsuite CVP_1_0_0 --offline --report http://<test_host_ip>:<testapi_port>/api/v1/results
+   $ dovetail run --offline --report http://<test_host_ip>:<testapi_port>/api/v1/results
 
-Until the official test suite is approved and released, you can use
-the *proposed_tests* for your trial runs, like this.
+Here is an example of running mandatory test areas.
 
 .. code-block:: bash
 
-   $ dovetail run --testsuite proposed_tests --testarea mandatory --report http://192.168.135.2:8000/api/v1/results
+   $ dovetail run --offline --testarea mandatory --report http://192.168.135.2:8000/api/v1/results
    2017-09-29 07:00:55,718 - run - INFO - ================================================
-   2017-09-29 07:00:55,718 - run - INFO - Dovetail compliance: proposed_tests!
+   2017-09-29 07:00:55,718 - run - INFO - Dovetail compliance: cvp.0.8.0!
    2017-09-29 07:00:55,718 - run - INFO - ================================================
    2017-09-29 07:00:55,719 - run - INFO - Build tag: daily-master-f0795af6-a4e3-11e7-acc5-0242ac110004
    2017-09-29 07:00:55,956 - run - INFO - >>[testcase]: dovetail.osinterop.tc001