aboutsummaryrefslogtreecommitdiffstats
path: root/docs/configguide/yardstick_testcases/testcase_description_v2_template.rst
blob: 1b8754b05b013f2c7d82b09d605346a583560143 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
.. Template to be used for test case descriptions in Yardstick Project.
   Write one .rst per test case.
   Upload the .rst for the test case in /docs/source/yardstick directory.
   Review in Gerrit.

*************************************
Yardstick Test Case Description TCXXX
*************************************

+-----------------------------------------------------------------------------+
|test case slogan e.g. Network Latency                                        |
|                                                                             |
+--------------+--------------------------------------------------------------+
|test case id  | e.g. OPNFV_YARDSTICK_TC001_NW Latency                        |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|metric        | what will be measured, e.g. latency                          |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|test purpose  | describe what is the purpose of the test case                |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|configuration | what .yaml file to use, state SLA if applicable, state       |
|              | test duration, list and describe the scenario options used in|
|              | this TC and also list the options using default values.      |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|test tool     | e.g. ping                                                    |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|references    | e.g. RFCxxx, ETSI-NFVyyy                                     |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|applicability | describe variations of the test case which can be            |
|              | performend, e.g. run the test for different packet sizes     |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|pre-test      | describe configuration in the tool(s) used to perform        |
|conditions    | the measurements (e.g. fio, pktgen), POD-specific            |
|              | configuration required to enable running the test            |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|test sequence | description and expected result                              |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|step 1        | use this to describe tests that require sveveral steps e.g   |
|              | collect logs.                                                |
|              |                                                              |
|              | Result: what happens in this step e.g. logs collected        |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|step 2        | remove interface                                             |
|              |                                                              |
|              | Result: interface down.                                      |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|step N        | what is done in step N                                       |
|              |                                                              |
|              | Result: what happens                                         |
|              |                                                              |
+--------------+--------------------------------------------------------------+
|test verdict  | expected behavior, or SLA, pass/fail criteria                |
|              |                                                              |
+--------------+--------------------------------------------------------------+