summaryrefslogtreecommitdiffstats
path: root/tests/opnfv/test_cases/opnfv_yardstick_tc037.yaml
diff options
context:
space:
mode:
authorchenjiankun <chenjiankun1@huawei.com>2017-01-12 07:50:30 +0000
committerchenjiankun <chenjiankun1@huawei.com>2017-01-20 01:58:50 +0000
commit75f55c05789beb4fbe2391d33349058bba4ea5c0 (patch)
tree7372165d15f83de442fa2a5778ee540ae2ced7c0 /tests/opnfv/test_cases/opnfv_yardstick_tc037.yaml
parent8f4cc883d89e997320d68c653a12d59f8fba308b (diff)
Create API to get a list of all test cases
JIRA: YARDSTICK-456 Currently we do not have a API to get a list of all test cases; Currently the test case info is from the comment; So I create a API to get a list of all test cases; And create a 'description' attribute to record info of a test case; And use the CLI call this API; Change-Id: Ife800600446683664097835c7b9f11899c85771d Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
Diffstat (limited to 'tests/opnfv/test_cases/opnfv_yardstick_tc037.yaml')
-rw-r--r--tests/opnfv/test_cases/opnfv_yardstick_tc037.yaml18
1 files changed, 9 insertions, 9 deletions
diff --git a/tests/opnfv/test_cases/opnfv_yardstick_tc037.yaml b/tests/opnfv/test_cases/opnfv_yardstick_tc037.yaml
index cd42098d2..0db490a15 100644
--- a/tests/opnfv/test_cases/opnfv_yardstick_tc037.yaml
+++ b/tests/opnfv/test_cases/opnfv_yardstick_tc037.yaml
@@ -1,15 +1,15 @@
---
-# Yardstick TC037 config file
-# Measure network throughput and packet loss using pktgen.
-# Different amounts of flows are tested with, from 2 up to 1001000.
-# All tests are run 2 times each. First 2 times with the least
-# amount of ports, then 2 times with the next amount of ports,
-# and so on until all packet sizes have been run with.
-#
-# During the measurements system load and network latency are
-# recorded/measured using ping and mpstat, respectively.
schema: "yardstick:task:0.1"
+description: >
+ Yardstick TC037 config file;
+ Measure network throughput and packet loss using pktgen;
+ Different amounts of flows are tested with, from 2 up to 1001000;
+ All tests are run 2 times each. First 2 times with the least
+ amount of ports, then 2 times with the next amount of ports,
+ and so on until all packet sizes have been run with;
+ During the measurements system load and network latency are
+ recorded/measured using ping and mpstat, respectively;
scenarios:
-