aboutsummaryrefslogtreecommitdiffstats
path: root/docs/configguide/yardstick_testcases/testcase_description_v2_template.rst
diff options
context:
space:
mode:
authorAna C <ana.cunha@ericsson.com>2016-02-10 19:07:13 +0100
committerAna Cunha <ana.cunha@ericsson.com>2016-02-11 15:05:18 +0000
commit95cdd0ea41e3892422de92f13fac39871585706e (patch)
treed8703d6411af6614b299a1005495c389327793ad /docs/configguide/yardstick_testcases/testcase_description_v2_template.rst
parent5f2938cc116f5c8769317e043440d79a0fb2045f (diff)
Add license info and update structure
This change adds license to all .rst files under userguide. It also combines all configguide files into user guide. New reference.rst with list of links. Updated glossary, removed separate directories for apexlake and yardstick framework. Change-Id: I6532ed073905b0fa85a17e759ea7dc3c24acb91f Signed-off-by: Ana C <ana.cunha@ericsson.com> (cherry picked from commit 702eebbf78b29fb9046436dd71575b4f210f4731)
Diffstat (limited to 'docs/configguide/yardstick_testcases/testcase_description_v2_template.rst')
-rw-r--r--docs/configguide/yardstick_testcases/testcase_description_v2_template.rst64
1 files changed, 0 insertions, 64 deletions
diff --git a/docs/configguide/yardstick_testcases/testcase_description_v2_template.rst b/docs/configguide/yardstick_testcases/testcase_description_v2_template.rst
deleted file mode 100644
index 1b8754b05..000000000
--- a/docs/configguide/yardstick_testcases/testcase_description_v2_template.rst
+++ /dev/null
@@ -1,64 +0,0 @@
-.. 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 |
-| | |
-+--------------+--------------------------------------------------------------+