summaryrefslogtreecommitdiffstats
path: root/docs/testing
diff options
context:
space:
mode:
Diffstat (limited to 'docs/testing')
-rw-r--r--docs/testing/developer/devguide/overview.rst12
-rw-r--r--docs/testing/developer/devguide/posca_guide.rst29
2 files changed, 34 insertions, 7 deletions
diff --git a/docs/testing/developer/devguide/overview.rst b/docs/testing/developer/devguide/overview.rst
index f561bfab..f2e8bff1 100644
--- a/docs/testing/developer/devguide/overview.rst
+++ b/docs/testing/developer/devguide/overview.rst
@@ -20,7 +20,7 @@ Virtual switch test framework(VSTF) is also introduced,
which is an test framework used for vswitch performance test.
Colorado: rubbos is refactored by using puppet, which makes it quite flexible
-to configure with different number of load generator(Client), worker(tomcat).
+to configure with different number of load generator (Client), worker (tomcat).
vstf is refactored by extracting the test case's configuration information.
Danube: posca testsuite is introduced to implementing stress (factor), scenario and
@@ -30,7 +30,7 @@ community CI pipeline. Rubbos and VSTF are not supported any more.
Integration Description
=======================
+-------------+----------------------+----------------------+
-| Release | integrated installer | Supported Testsuite |
+| Release | Integrated Installer | Supported Testsuite |
+-------------+----------------------+----------------------+
| Brahmaputra | Fuel | Rubbos, VSTF |
+-------------+----------------------+----------------------+
@@ -42,6 +42,10 @@ Integration Description
Test suite & Test case Description
==================================
+--------+-------------------------------+
+|POSCA | posca_factor_ping |
+| +-------------------------------+
+| | posca_factor_system_bandwidth |
++--------+-------------------------------+
|Rubbos | rubbos_basic |
| +-------------------------------+
| | rubbos_TC1101 |
@@ -70,7 +74,3 @@ Test suite & Test case Description
| +-------------------------------+
| | vstf_Tu3 |
+--------+-------------------------------+
-|posca | posca_factor_ping |
-| +-------------------------------+
-| | posca_factor_system_bandwidth |
-+--------+-------------------------------+
diff --git a/docs/testing/developer/devguide/posca_guide.rst b/docs/testing/developer/devguide/posca_guide.rst
index 5d101a6e..ae6c2481 100644
--- a/docs/testing/developer/devguide/posca_guide.rst
+++ b/docs/testing/developer/devguide/posca_guide.rst
@@ -138,10 +138,37 @@ If you want to clean the dockers that established during the test, you can excut
docker-compose -f docker/bottleneck-compose/docker-compose.yml down -d
docker ps -a | grep 'influxdb' | awk '{print $1}' | xargs docker rm -f >/dev/stdout
+Or you can just run the following command
+
+.. code-block:: bash
+
+ bash run_tests.sh --cleanup
+
+Note that you can also add cleanup parameter when you run a test case. Then environment will be automatically cleaned up when
+completing the test.
Run POSCA through Community CI
==============================
-* POSCA test cases are runned by OPNFV CI now. See https://build.opnfv.org for more information.
+POSCA test cases are runned by OPNFV CI now. See https://build.opnfv.org for details of the building jobs.
+Each building job is set up to execute a single test case. The test results/logs will be printed on the web page and
+reported automatically to community MongoDB. There are two ways to report the results.
+
+1. Report testing result by shell script
+
+.. code-block:: bash
+
+ bash run_tests.sh [-h|--help] [-s <testsuite>] [-c <testcase>] --report
+
+2. Report testing result by python interpreter
+
+.. code-block:: bash
+
+ docker-compose -f docker/bottleneck-compose/docker-compose.yml up -d
+ docker pull tutum/influxdb:0.13
+ sleep 5
+ REPORT="True"
+ POSCA_SCRIPT="/home/opnfv/bottlenecks/testsuites/posca"
+ docker exec bottleneckcompose_bottlenecks_1 python ${POSCA_SCRIPT}/run_posca.py [testcase <testcase>] [teststory <teststory>] REPORT
Test Result Description
=======================