{ "id": 2, "title": "Yardstick-TC002", "originalTitle": "Yardstick-TC002", "tags": [ "yardstick-tc" ], "style": "dark", "timezone": "browser", "editable": true, "hideControls": false, "sharedCrosshair": false, "rows": [ { "collapse": false, "editable": true, "height": "", "panels": [ { "content": "
Evaluation of network latency (RTT - round trip time) between two VM instances running on different physical blades.\nFor more information see TC002
\n.. Template to be used for test case descriptions in QTIP Project.
Write one .rst per test case.
Borrowed Heavily from Yardstick
Upload the .rst for the test case in /docs/ directory.
Review in Gerrit.
Test Case Description
=====================
+-----------------------------------------------------------------------------+
|test case slogan e.g. Network throughput |
+==============+==============================================================+
|test case id | e.g. qtip_throughput |
+--------------+--------------------------------------------------------------+
|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 | step | description | result |
| +------+----------------------------------+--------------------+
| | 1 | use this to describe tests that | what happens in |
| | | require several steps e.g. | this step |
| | | step 1 collect logs | e.g. logs collected|
| +------+----------------------------------+--------------------+
| | 2 | remove interface | interface down |
| +------+----------------------------------+--------------------+
| | N | what is done in step N | what happens |
+--------------+------+----------------------------------+--------------------+
|test verdict | expected behavior, or SLA, pass/fail criteria |
+--------------+--------------------------------------------------------------+