summaryrefslogtreecommitdiffstats
path: root/tests/opnfv/test_cases/opnfv_yardstick_tc008.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_tc008.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_tc008.yaml')
-rw-r--r--tests/opnfv/test_cases/opnfv_yardstick_tc008.yaml19
1 files changed, 10 insertions, 9 deletions
diff --git a/tests/opnfv/test_cases/opnfv_yardstick_tc008.yaml b/tests/opnfv/test_cases/opnfv_yardstick_tc008.yaml
index a2f5f3adc..89986f7f1 100644
--- a/tests/opnfv/test_cases/opnfv_yardstick_tc008.yaml
+++ b/tests/opnfv/test_cases/opnfv_yardstick_tc008.yaml
@@ -1,15 +1,16 @@
---
-# Yardstick TC008 config file
-# Measure network throughput and packet loss using Pktgen.
-# Different amount of flows, from 2 up to 1001000, in combination
-# with different packet sizes are run in each test.
-# Each combination of packet size and flow amount is run 10 times.
-# First 10 times with the smallest packet size, starting with the
-# least amount of ports/flows, then next amount of ports with same
-# packet size, and so on. The test sequence continues with the next
-# packet size, with same ports/flows sequence as before.
schema: "yardstick:task:0.1"
+description: >
+ Yardstick TC008 config file;
+ Measure network throughput and packet loss using Pktgen;
+ Different amount of flows, from 2 up to 1001000, in combination
+ with different packet sizes are run in each test.
+ Each combination of packet size and flow amount is run 10 times.
+ First 10 times with the smallest packet size, starting with the
+ least amount of ports/flows, then next amount of ports with same
+ packet size, and so on. The test sequence continues with the next
+ packet size, with same ports/flows sequence as before.
scenarios:
{% for pkt_size in [64, 128, 256, 512, 1024, 1280, 1518] %}