summaryrefslogtreecommitdiffstats
path: root/docs/dovetailtool/dovetail.tool.configuration.rst
diff options
context:
space:
mode:
authorMatthewLi <matthew.lijun@huawei.com>2017-01-14 04:08:13 -0500
committerMatthewLi <matthew.lijun@huawei.com>2017-01-19 03:38:07 -0500
commit9dee0a4b210d9c682464f7cf8052b803139b1b95 (patch)
treedc123734fc8951d10858ef40bbbc054f32e8c917 /docs/dovetailtool/dovetail.tool.configuration.rst
parentc2401cd1bf3898aebeef08ca699072b1dca683f0 (diff)
dovetail tool userguide document
JIRA: DOVETAIL-182 Change-Id: Icbfa347dda3840520484d10b9d539da9c8f1d31c Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
Diffstat (limited to 'docs/dovetailtool/dovetail.tool.configuration.rst')
-rw-r--r--docs/dovetailtool/dovetail.tool.configuration.rst35
1 files changed, 0 insertions, 35 deletions
diff --git a/docs/dovetailtool/dovetail.tool.configuration.rst b/docs/dovetailtool/dovetail.tool.configuration.rst
deleted file mode 100644
index 8e97e73c..00000000
--- a/docs/dovetailtool/dovetail.tool.configuration.rst
+++ /dev/null
@@ -1,35 +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 Technologies Co.,Ltd and others.
-
-=========================
-Testcase Template Syntax
-=========================
-
-The testcases used for compliance and certification are defined in the ``dovetail/testcase`` directory,
-which are defined in yaml format. Take the testcase ``ipv6.tc001.yml`` as an example, it is shown as:
-
-::
-
- dovetail.ipv6.tc001:
- name: dovetail.ipv6.tc001
- objective: VIM ipv6 operations, to create/delete network, port and subnet in bulk operation
- scripts:
- type: functest
- testcase: tempest_smoke_serial
- sub_testcase_list:
- - tempest.api.network.test_networks.BulkNetworkOpsIpV6Test.test_bulk_create_delete_network
- - tempest.api.network.test_networks.BulkNetworkOpsIpV6Test.test_bulk_create_delete_port
- - tempest.api.network.test_networks.BulkNetworkOpsIpV6Test.test_bulk_create_delete_subnet
-
-- At least three sections named 'name', 'objective', 'scripts' must be included
-- Section 'name' distinguishes different test cases used for compliance and certification,
- and should start with ``dovetail.``
-- Section 'objective' describes what this testcase does
-- Section 'scripts' has subsections such as 'type', 'testcase' and 'sub_testcase_list'
-- Two kinds of 'type' is supported by now, functest and yardstick
-- For functest, the 'testcase' represents the testcases in slicing/tier,
- 'sub_testcase_list' represents the testcases in this slicing compliance and certification will use.
- For yardstick, since it is not sliced by now, 'sub_testcase_list' is not needed, only to edit the 'testcase' part
- such as ``yardstick_tc027``