summaryrefslogtreecommitdiffstats
path: root/docs/testing/user/userguide
diff options
context:
space:
mode:
authorYang Yu <Gabriel.yuyang@huawei.com>2017-12-14 16:39:34 +0800
committerYang Yu <Gabriel.yuyang@huawei.com>2017-12-15 12:07:54 +0800
commitec584918ae66e92c7d8b5ff41b0df4ad391d2349 (patch)
treec28367d69ba27f08f7f86d0eb5e10bfdddbea38a /docs/testing/user/userguide
parent5c1e34c97ceaa2a3b5a0b8e032eb041c52858808 (diff)
Docs update for E 5.1
Change-Id: I53972edc64398339463824d5f8d7193a6e15481f Signed-off-by: Yang Yu <Gabriel.yuyang@huawei.com>
Diffstat (limited to 'docs/testing/user/userguide')
-rw-r--r--docs/testing/user/userguide/overview.rst22
-rw-r--r--docs/testing/user/userguide/posca_guide.rst16
2 files changed, 21 insertions, 17 deletions
diff --git a/docs/testing/user/userguide/overview.rst b/docs/testing/user/userguide/overview.rst
index 5d76c76c..746f24c4 100644
--- a/docs/testing/user/userguide/overview.rst
+++ b/docs/testing/user/userguide/overview.rst
@@ -58,17 +58,17 @@ Integration Description
Test suite & Test case Description
==================================
-+--------+-------------------------------+
-|POSCA | posca_factor_ping |
-| +-------------------------------+
-| | posca_factor_system_bandwidth |
-| +-------------------------------+
-| | posca_facotor_througputs |
-| +-------------------------------+
-| | posca_feature_scaleup |
-| +-------------------------------+
-| | posca_feature_scaleout |
-+--------+-------------------------------+
++--------+-------------------------------------+
+|POSCA | posca_factor_ping |
+| +-------------------------------------+
+| | posca_factor_system_bandwidth |
+| +-------------------------------------+
+| | posca_facotor_soak_througputs |
+| +-------------------------------------+
+| | posca_feature_vnf_scale_up |
+| +-------------------------------------+
+| | posca_feature_vnf_scale_out |
++--------+-------------------------------------+
As for the abandoned test suite in the previous Bottlenecks releases, please
refer to http://docs.opnfv.org/en/stable-danube/submodules/bottlenecks/docs/testing/user/userguide/deprecated.html.
diff --git a/docs/testing/user/userguide/posca_guide.rst b/docs/testing/user/userguide/posca_guide.rst
index fc811b5e..ec623d03 100644
--- a/docs/testing/user/userguide/posca_guide.rst
+++ b/docs/testing/user/userguide/posca_guide.rst
@@ -30,7 +30,7 @@ Scopes of the POSCA testsuite:
b) Parameters choosing and Algorithms.
Test stories of POSCA testsuite:
- a) Factor test (Stress test): base test cases that Feature test and Optimization will be dependant on.
+ a) Factor test (Stress test): base test cases that Feature test and Optimization will be dependant on or stress test to validate system.
b) Feature test: test cases for features/scenarios.
c) Optimization test: test to tune the system parameter.
@@ -45,6 +45,8 @@ Preinstall Packages
* Docker: https://docs.docker.com/engine/installation/
* For Ubuntu, please refer to https://docs.docker.com/engine/installation/linux/ubuntu/
+[Since Euphrates release, the docker-compose package is not required.]
+
* Docker-Compose: https://docs.docker.com/compose/
.. code-block:: bash
@@ -97,8 +99,10 @@ Edit admin_rc.sh and add the following line
export OS_CACERT=/tmp/os_cacert
-If you are using compass, fuel, apex or joid to deploy your openstack
-environment, you could use the following command to get the required files.
+If you have deployed your openstack environment by compass,
+you could use the following command to get the required files. For Fuel, Apex and JOID installer, we only provide limited support now
+for retrieving the configuration/description files. If you find that the following command can not do the magic, you should put the
+required files in /tmp manually.
.. code-block:: bash
@@ -116,9 +120,9 @@ Executing Specified Testcase
bottlenecks testcase|teststory run <testname>
- For the *testcase* command, testname should be as the same name of the test case configuration file located in testsuites/posca/testcase_cfg.
- For stress tests in Danube/Euphrates, *testcase* should be replaced by either *posca_factor_ping* or *posca_factor_system_bandwidth*.
- For the *teststory* command, a user can specify the test cases to be executed by defining it in a teststory configuration file located in testsuites/posca/testsuite_story. There is also an example there named *posca_factor_test*.
+For the *testcase* command, testname should be as the same name of the test case configuration file located in testsuites/posca/testcase_cfg.
+For stress tests in Danube/Euphrates, *testcase* should be replaced by either *posca_factor_ping* or *posca_factor_system_bandwidth*.
+For the *teststory* command, a user can specify the test cases to be executed by defining it in a teststory configuration file located in testsuites/posca/testsuite_story. There is also an example there named *posca_factor_test*.
2. There are also other 2 ways to run test cases and test stories.