summaryrefslogtreecommitdiffstats
path: root/docs/platformoverview/testcasesframework.rst
diff options
context:
space:
mode:
authorulik <ulrich.kleber@huawei.com>2016-02-23 13:35:01 +0100
committerChristopher Price <christopher.price@ericsson.com>2016-02-24 21:48:27 +0000
commit0d5c7b5b68fda47b1ee908ea9e002b30881ed83b (patch)
tree9305e041b735f951846a2dd1503fba4b7e03ba04 /docs/platformoverview/testcasesframework.rst
parentd4134280f9acbf523454673931155ab4af9b42a0 (diff)
Review and finalize platformoverview
Jira: DOCS-42 Collected all comments. Many comments done, open points marked in commentary (".. text") Patchset 2: resolve most of the comments. Don't merge yet. Change-Id: I3d676a6510ff3c3190110773649265a182b6f762 Signed-off-by: ulik <ulrich.kleber@huawei.com>
Diffstat (limited to 'docs/platformoverview/testcasesframework.rst')
-rw-r--r--docs/platformoverview/testcasesframework.rst110
1 files changed, 105 insertions, 5 deletions
diff --git a/docs/platformoverview/testcasesframework.rst b/docs/platformoverview/testcasesframework.rst
index 6a40e282d..301e1e0b4 100644
--- a/docs/platformoverview/testcasesframework.rst
+++ b/docs/platformoverview/testcasesframework.rst
@@ -2,9 +2,109 @@
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, Huawei
-=======================
-Testcases and Framework
-=======================
+=================
+Testing ecosystem
+=================
+
+Testing is a key area and also a challenge for OPNFV in order to be able to
+verify and validate the platform we are creating.
+
+This is a complex task as we have to test the integration of the components,
+the functionality we are creating and using and we have to verify
+that the platform is suitable for telecom applications.
+We do testing in an automated fashion by using several test tools and frameworks in our CI/CD pipeline.
+
+This chapter gives an overview about our testing tools and activities.
+
+
+Release verification
+====================
+
+OPNFV releases the target platform together with the deployment tools in a set of scenarios
+that provides choices regarding the deployed components and the available features.
+The scenarios and the provided functionality are tested automatically in the CI/CD pipeline
+mentioned above and they are considered to be ready for release after
+at least 4 successful consecutive iterations.
+
+The functional testing and the platform validation are divided between two projects called Functest and Yardstick.
+
+Functest
+--------
+
+Functest provides a functional testing framework along with a set of test suites
+and test cases that test and verify OPNFV platform functionality.
+The scope of Functest and relevant test cases can be found in its
+`user guide <http://artifacts.opnfv.org/functest/brahmaputra/docs/userguide/userguide.pdf>`_.
+
+In Brahmaputra, Functest is focusing on OpenStack and SDN controllers deployment testing.
+Its testing framework combines a number of testing tools
+to verify the key components of OPNFV platform running successfully.
+For example, Rally and Tempest are integrated for OpenStack basic functional testing and benchmark,
+Robot is used for ODL testing, and Teston is integrated for ONOS testing.
+Besides these, Functest also includes tests by deploying candidate VNFs such as vPing and vIMS, and testing their basic functionality.
+
+Yardstick
+---------
+
+Yardstick is a testing project for verifying the infrastructure compliance when running VNF applications.
+Yardstick can benchmark a number of characteristics/performance vectors about the infrastructure,
+that makes it become a useful pre-deployment NFVI testing tools.
+
+Yardstick is also a flexible testing framework supporting OPNFV feature testing by the various projects in OPNFV.
+Projects can plug in their test cases for specific features easily.
+
+The detail of Yardstick project can be found in the
+`yardstick user guide <http://artifacts.opnfv.org/yardstick/brahmaputra/docs/user_guides_framework/user_guides_framework.pdf>`_.
+
+There are two types of test cases in Yardstick: Yardstick generic test cases and OPNFV feature test cases.
+Yardstick generic test cases include basic characteristics benchmarking in compute/storage/network area.
+OPNFV feature test cases include basic telecom feature testing from OPNFV projects,
+for example nfv-kvm, sfc, ipv6, Parser, Availability and SDN VPN.
+
+All of the Yardstick test cases are listed on
+`<http://artifacts.opnfv.org/yardstick/docs/configguide_yardstick_testcases/03-list-of-tcs.html>`_
+
+
+Additional Testing
+==================
+
+Besides the test suites and cases for release verification, there are some additional testing
+for specific feature or characteristics on OPNFV platform.
+These testing framework and test cases may include some specific needs,
+such as extended measurements, or additional testing stimuli, or tests which cause disturbances on the environment.
+These additional testing can provide a more complete evaluation about OPNFV platform deployment.
+
+Qtip
+----
+
+Qtip is a performance benchmark testing project by using a "Bottom-Up" approach
+in characterizing and benchmarking OPNFV platform.
+Qtip aims to benchmark the performance of components for a quantitative analysis and doesn't deal with validation of the platform.
+
+In Brahmaputra, Qtip develops a flexible framework,
+adds a number of test cases covering compute/storage/network area,
+and compares these benchmarks on a bare metal machine vs a VM.
+These contrastive result can be used to evaluate the performance of these components on the OPNFV platform basically.
+
+VSPERF
+------
+
+VSPERF will develop a generic and architecture agnostic vSwitch testing framework and associated tests,
+that will serve as a basis for validating the suitability of different vSwitch implementations
+in a Telco NFV deployment environment.
+The output of this project will be utilized as part of OPNFV Platform and VNF level testing and validation.
+
+Bottlenecks
+-----------
+
+Bottlenecks will provide a framework to find system bottlenecks
+by testing and verifying OPNFV infrastructure in a staging environment before committing it to a production environment.
+The Bottlenecks framework can not only find specific system limitations and bottlenecks,
+but also the root cause of these bottlenecks.
+
+In Brahmaputra, Bottlenecks includes two test cases:
+rubbos and vstf. These test cases are executed on OPNFV community pods,
+and test result report are visible on the community testing dashboard.
+
+
-Editors note:
-Just a high level description about the different types of tests and the role of yardstick as central framework.