summaryrefslogtreecommitdiffstats
path: root/docs/testsuites/ipv6/testspecification.rst
diff options
context:
space:
mode:
authorChristopherPrice <christopher.price@ericsson.com>2016-08-08 16:07:05 +0200
committerChristopherPrice <christopher.price@ericsson.com>2016-08-09 15:50:39 +0200
commite7316237cc9f5b469c53682af6f57099d42a3279 (patch)
tree3cc4559e5c2de6c2b83b3d2563130a9c11c34983 /docs/testsuites/ipv6/testspecification.rst
parent5e04ff0326fc4f6ba23b5ac7abfe3fc04ace18f7 (diff)
Proposing a Dovetail test suite structure for IPv6
Adding the first draft of the IPv6 test suite. This patch attempts to start the documentation according to the proposal on https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269 The text is neither complete nor accurate at this stage, this patch is intended to establish a concrete dialog for how we structure our test suites and reference test cases. Change-Id: I156ddafa3e8b7630390523864490426fc742eb3a Signed-off-by: ChristopherPrice <christopher.price@ericsson.com>
Diffstat (limited to 'docs/testsuites/ipv6/testspecification.rst')
-rw-r--r--docs/testsuites/ipv6/testspecification.rst54
1 files changed, 54 insertions, 0 deletions
diff --git a/docs/testsuites/ipv6/testspecification.rst b/docs/testsuites/ipv6/testspecification.rst
new file mode 100644
index 00000000..6f7caba8
--- /dev/null
+++ b/docs/testsuites/ipv6/testspecification.rst
@@ -0,0 +1,54 @@
+.. 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
+
+===============================================
+Test specification - Service VM as IPv6 vRouter
+===============================================
+
+Draft to be worked on, this represents the YardStick test but I would suggest we need to break
+this into a set of tests which provide more details per action with boundary validation.
+
+Test Item
+=========
+
+TBD -> IPv6 Ping...
+
+Identify the items or features to be tested by this test case. The item description and
+definition can be referenced from any one of several sources, depending on the level of the
+test case specification. It may be a good idea to reference the source documents as well.
+
+Environmental requirements
+==========================
+
+TBD
+
+Preconditions and procedural requirements
+=========================================
+
+TBD
+
+.. <Start>
+.. this section may be iterated over for a set of simillar test cases that would be run as one.
+
+Input Specifications
+====================
+
+TBD
+
+Output Specifications
+=====================
+
+TBD
+
+.. <End>
+
+Test Reporting
+==============
+
+The test report for this test case will be generated with links to relevant data sources.
+This section can be updated once we have a template for the report in place.
+
+http://testresults.opnfv.org/grafana/dashboard/db/yardstick-tc027
+
+