summaryrefslogtreecommitdiffstats
path: root/docs/testsuites/ipv6/testplan.rst
diff options
context:
space:
mode:
authorBin Hu <bh526r@att.com>2016-09-08 15:27:26 -0700
committerBin Hu <bh526r@att.com>2016-09-27 08:15:02 -0700
commitc3e531c8bad549ec48510af977b488d8e6da5bef (patch)
treeacade77daf11e33b58b6d2c8001f4969e38c1abf /docs/testsuites/ipv6/testplan.rst
parente7316237cc9f5b469c53682af6f57099d42a3279 (diff)
IPv6 test cases: Test case specification document example
JIRA: DOVETAIL-9 1. We are keeping the test methodology simple and easy. We are reusing existing tests as much as we can from IPv6 projects and Tempest API and Scenario tests, which are run in FuncTest and Yardstick. 2. We modified "testplan.rst" to briefly describe the test plan, i.e. current IPv6 test cases for platform compliance, which have passed FuncTest and Yardstick test in Arno and Brahmaputra releases. We also leave room for additional IPv6 test cases if there are more contributions down the road 3. Original "designspecification.rst", "testprocedure.rst" and "testspecification.rst" are not applicable any more here. The test design, setup, and execution procedure related specification are covered by each test case. 4. Thus "index.rst" only covers "testplan.rst" and the list of test cases. 5. Two examples of test case specification documents are provided "ipv6.tc001.specification.rst" "ipv6.tc026.specification.rst" 6. A complete set of current IPv6 test cases are listed in "ipv6_all_testcases.rst". Once template is agreed, we will converted it into specific test case document. For more background of IPv6, and its features and technical details, please see: https://wiki.opnfv.org/display/ipv6/IPv6+Home http://artifacts.opnfv.org/ipv6/docs/installationprocedure/index.html Change-Id: I7e47c73c0f02a407df278c93a3da2142b5cc86e5 Signed-off-by: Bin Hu <bh526r@att.com>
Diffstat (limited to 'docs/testsuites/ipv6/testplan.rst')
-rw-r--r--docs/testsuites/ipv6/testplan.rst46
1 files changed, 10 insertions, 36 deletions
diff --git a/docs/testsuites/ipv6/testplan.rst b/docs/testsuites/ipv6/testplan.rst
index 1d03d812..3470e7a6 100644
--- a/docs/testsuites/ipv6/testplan.rst
+++ b/docs/testsuites/ipv6/testplan.rst
@@ -1,60 +1,34 @@
.. This work is licensed under a Creative Commons Attribution 4.0 International License.
.. http://creativecommons.org/licenses/by/4.0
-.. (c) Christopher Price (Ericsson AB) and others
+.. (c) OPNFV
===============================
-OPNFV IPv6 compliance test plan
+OPNFV IPv6 Compliance Test Plan
===============================
Introduction
============
-The IPv6 compliance test plan outlines the method for testing IPv6 compliance to the OPNFV
-platform behaviours and features of IPv6 enabled VNFi platforms.
+The IPv6 compliance test plan outlines the method for testing IPv6 Tenant Network feature
+compliance with the OPNFV platform.
Scope
-----
-In this document, and throughout the test suite, the system under test (SUT) is defined as
-the combination of the VNFi and VIM as defined by the ETSI NVF ISG (need reference).
+This test, and other tests in the test suite, are designed to verify an entire SUT,
+and not any individual component of the system.
Test suite scope and procedures
===============================
-The IPv6 compliance test suite will evaluate the ability for a NVFi platform and VIM to provide
-needed IPv6 features and functionality for use as an IPv6 enabled platform.
+The IPv6 compliance test suite will evaluate the ability for a SUT to support IPv6
+Tenant Network features and functionality provided by OPNFV platform.
-An IPv6 enabled platform needs to be able to demonstrate the ability to support for instance;
-the ability to assign IPv6 addresses using SLAAC or stateful and stateless DHCPv6, the ability
-to securely send a receive IPv6 traffic to an external network, support for multiple address
-and dual stack interfaces. For a complete list of the test cases refer to the test case specification [2]_.
-
-As the test suite runs as an external entity the system under test includes both the behaviours
-and interfaces specified for the test. It is expected that the system under test (SUT) interfaces
-are compliant with the specifications or references supplied in the test case design [1]_ document.
-In addition the behaviours exhibited by the platform should comply to the referred standards
-or behaviours as outlined in the test case design [1]_ document.
+Please refer to the complete list of the test cases for details.
Test suite execution
====================
-The test suite expects to interact with a system in an IPv6 enabled and ready state. An IPv6
-enabled system can be installed using an IPv6 enabled OPNFV scenario, or if you are not using
-an OPNFV scenario ensure you have configured your system to use IPv6, in this case also pay
-specific attention to the details of specific test preconditions captured in the
-test procedure specification [3]_.
-
-The test suite is designed to be run from an external server, the jump host, with access to the
-control and network interfaces in order that it interacts with the SUT as an external entity.
-The test suite will be executed by the test suite operator via scripts to be executed on the
-jump host, or by leveraging the OPNFV infrastructure to execute an IPv6 compliance test job
-from the jump host. Test cases may instantiate additional workloads on the SUT as part of the
-test cases being executed, the system shall be returned to it's original state once the test
-suite has completed.
-
-
+Please refer to each test case for specific setup and execution procedure.
.._[1]: http://www.opnfv.org
-.._[2]: http://www.opnfv.org
-.._[3]: http://www.opnfv.org
-