summaryrefslogtreecommitdiffstats
path: root/docs/release/userguide/_testcase_description.rst
diff options
context:
space:
mode:
authorYujun Zhang <zhang.yujunz@zte.com.cn>2017-02-21 06:35:35 +0000
committerGerrit Code Review <gerrit@opnfv.org>2017-02-21 06:35:35 +0000
commit642ccf1b4f905d779b33b224ace16c3c0abf25a1 (patch)
tree07811518c2f6f3d3610cf0172a8e0ada6043cf9c /docs/release/userguide/_testcase_description.rst
parent28c44a46d38c1bd79b54488c30be2f6fcee4bf8f (diff)
parentb9de54adc5963e54303dccf5930f6b20cc445dae (diff)
Merge "Migrate to Danube document guide"
Diffstat (limited to 'docs/release/userguide/_testcase_description.rst')
-rw-r--r--docs/release/userguide/_testcase_description.rst46
1 files changed, 46 insertions, 0 deletions
diff --git a/docs/release/userguide/_testcase_description.rst b/docs/release/userguide/_testcase_description.rst
new file mode 100644
index 00000000..d60ca949
--- /dev/null
+++ b/docs/release/userguide/_testcase_description.rst
@@ -0,0 +1,46 @@
+.. 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 |
++--------------+--------------------------------------------------------------+
+