summaryrefslogtreecommitdiffstats
path: root/docs/configguide/yardstick_testcases/opnfv_yardstick_tc040.rst
diff options
context:
space:
mode:
authorkubi <jean.gaoliang@huawei.com>2016-01-11 21:30:45 +0800
committerqi liang <liangqi1@huawei.com>2016-01-11 14:21:36 +0000
commit6c0b5d537c4933a1e71a1dd644227d9d48ff3f09 (patch)
treeb17393a5ef2916b0096d21f2c6080bf1baec1d0b /docs/configguide/yardstick_testcases/opnfv_yardstick_tc040.rst
parent02fe86335df21aa7c90bff1740db1444625110a1 (diff)
Test Case 040 Verify Parser Yang-to-Tosca
running Parser Yang-to-Tosca module as a tool, validating output against expected outcome. this patch is about task yaml and rst for test case description. JIRA:YARDSTICK-224 Signed-off-by: kubi <jean.gaoliang@huawei.com> Change-Id: Id254c5cf45de33b023bef889a58044a21ed0db43 Signed-off-by: kubi <jean.gaoliang@huawei.com> (cherry picked from commit 45e85a7f6df63ca4ca702f519ca19e5bcbb1bc23)
Diffstat (limited to 'docs/configguide/yardstick_testcases/opnfv_yardstick_tc040.rst')
-rw-r--r--docs/configguide/yardstick_testcases/opnfv_yardstick_tc040.rst60
1 files changed, 60 insertions, 0 deletions
diff --git a/docs/configguide/yardstick_testcases/opnfv_yardstick_tc040.rst b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc040.rst
new file mode 100644
index 000000000..044ccf193
--- /dev/null
+++ b/docs/configguide/yardstick_testcases/opnfv_yardstick_tc040.rst
@@ -0,0 +1,60 @@
+*************************************
+Yardstick Test Case Description TC040
+*************************************
+
+.. _Parser: https://wiki.opnfv.org/parser
+
++-----------------------------------------------------------------------------+
+|Verify Parser Yang-to-Tosca |
+| |
++--------------+--------------------------------------------------------------+
+|test case id | OPNFV_YARDSTICK_TC040 Verify Parser Yang-to-Tosca |
+| | |
++--------------+--------------------------------------------------------------+
+|metric | 1. tosca file which is converted from yang file by Parser |
+| | 2. result whether the output is same with expected outcome |
++--------------+--------------------------------------------------------------+
+|test purpose | To verify the function of Yang-to-Tosca in Parser. |
+| | |
++--------------+--------------------------------------------------------------+
+|configuration | file: opnfv_yardstick_tc040.yaml |
+| | |
+| | yangfile: the path of the yangfile which you want to convert |
+| | toscafile: the path of the toscafile which is your expected |
+| | outcome. |
+| | |
++--------------+--------------------------------------------------------------+
+|test tool | Parser |
+| | |
+| | (Parser is not part of a Linux distribution, hence it |
+| | needs to be installed. As an example see the |
+| | /yardstick/benchmark/scenarios/parser/parser_setup.sh for |
+| | how to install it manual. Of course, it will be installed |
+| | and uninstalled automatically when you run this test case |
+| | by yardstick) |
++--------------+--------------------------------------------------------------+
+|references | Parser_ |
+| | |
+| | |
++--------------+--------------------------------------------------------------+
+|applicability | Test can be configured with different path of yangfile and |
+| | toscafile to fit your real environment to verify Parser |
+| | |
++--------------+--------------------------------------------------------------+
+|pre-test | No POD specific requirements have been identified. |
+|conditions | it can be run without VM |
+| | |
++--------------+--------------------------------------------------------------+
+|test sequence | description and expected result |
+| | |
++--------------+--------------------------------------------------------------+
+|step 1 | parser is installed without VM, running Yang-to-Tosca module |
+| | to convert yang file to tosca file, validating output against|
+| | expected outcome. |
+| | |
+| | Result: Logs are stored. |
++--------------+--------------------------------------------------------------+
+|test verdict | Fails only if output is different with expected outcome |
+| | or if there is a test case execution problem. |
+| | |
++--------------+--------------------------------------------------------------+