summaryrefslogtreecommitdiffstats
path: root/docs/platformoverview/testcasesframework.rst
diff options
context:
space:
mode:
authorChristopherPrice <christopher.price@ericsson.com>2016-08-29 18:39:54 +0200
committerChristopherPrice <christopher.price@ericsson.com>2016-09-19 17:30:12 +0200
commit91ac9a64b9ebdf0c1b0c81144e8037f7efa6824e (patch)
treef146c39489e63c6072824b9d0a99fe785fde4fb2 /docs/platformoverview/testcasesframework.rst
parente042f556c6c25858f328cb6287c164b2514a2561 (diff)
Draft of the overview doc.
Change-Id: I13d4230591055c5e8c1f4daa469a6bf71993856e Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
Diffstat (limited to 'docs/platformoverview/testcasesframework.rst')
-rw-r--r--docs/platformoverview/testcasesframework.rst110
1 files changed, 0 insertions, 110 deletions
diff --git a/docs/platformoverview/testcasesframework.rst b/docs/platformoverview/testcasesframework.rst
deleted file mode 100644
index 73c9cd187..000000000
--- a/docs/platformoverview/testcasesframework.rst
+++ /dev/null
@@ -1,110 +0,0 @@
-.. This work is licensed under a Creative Commons Attribution 4.0 International License.
-.. http://creativecommons.org/licenses/by/4.0
-.. (c) OPNFV, Huawei
-
-=================
-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 the OPNFV platform are 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/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/brahmaputra/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.
-
-
-