Merge "Add test case description and task file for TC025"
[yardstick.git] / docs / configguide / yardstick_testcases / opnfv_yardstick_tc040.rst
1 *************************************
2 Yardstick Test Case Description TC040
3 *************************************
4
5 .. _Parser: https://wiki.opnfv.org/parser
6
7 +-----------------------------------------------------------------------------+
8 |Verify Parser Yang-to-Tosca                                                  |
9 |                                                                             |
10 +--------------+--------------------------------------------------------------+
11 |test case id  | OPNFV_YARDSTICK_TC040 Verify Parser Yang-to-Tosca            |
12 |              |                                                              |
13 +--------------+--------------------------------------------------------------+
14 |metric        | 1. tosca file which is converted from yang file by Parser    |
15 |              | 2. result whether the output is same with expected outcome   |
16 +--------------+--------------------------------------------------------------+
17 |test purpose  | To verify the function of Yang-to-Tosca in Parser.           |
18 |              |                                                              |
19 +--------------+--------------------------------------------------------------+
20 |configuration | file: opnfv_yardstick_tc040.yaml                             |
21 |              |                                                              |
22 |              | yangfile: the path of the yangfile which you want to convert |
23 |              | toscafile: the path of the toscafile which is your expected  |
24 |              | outcome.                                                     |
25 |              |                                                              |
26 +--------------+--------------------------------------------------------------+
27 |test tool     | Parser                                                       |
28 |              |                                                              |
29 |              | (Parser is not part of a Linux distribution, hence it        |
30 |              | needs to be installed. As an example see the                 |
31 |              | /yardstick/benchmark/scenarios/parser/parser_setup.sh for    |
32 |              | how to install it manual. Of course, it will be installed    |
33 |              | and uninstalled automatically when you run this test case    |
34 |              | by yardstick)                                                |
35 +--------------+--------------------------------------------------------------+
36 |references    | Parser_                                                      |
37 |              |                                                              |
38 |              |                                                              |
39 +--------------+--------------------------------------------------------------+
40 |applicability | Test can be configured with different path of yangfile and   |
41 |              | toscafile to fit your real environment to verify Parser      |
42 |              |                                                              |
43 +--------------+--------------------------------------------------------------+
44 |pre-test      |  No POD specific requirements have been identified.          |
45 |conditions    |  it can be run without VM                                    |
46 |              |                                                              |
47 +--------------+--------------------------------------------------------------+
48 |test sequence | description and expected result                              |
49 |              |                                                              |
50 +--------------+--------------------------------------------------------------+
51 |step 1        | parser is installed without VM, running Yang-to-Tosca module |
52 |              | to convert yang file to tosca file, validating output against|
53 |              | expected outcome.                                            |
54 |              |                                                              |
55 |              | Result: Logs are stored.                                     |
56 +--------------+--------------------------------------------------------------+
57 |test verdict  | Fails only if output is different with expected outcome      |
58 |              | or if there is a test case execution problem.                |
59 |              |                                                              |
60 +--------------+--------------------------------------------------------------+