summaryrefslogtreecommitdiffstats
path: root/behave_tests/features/non-regression.feature
diff options
context:
space:
mode:
authorfmenguy <francoisregis.menguy@orange.com>2021-03-11 20:33:36 +0100
committerfmenguy <francoisregis.menguy@orange.com>2021-04-27 16:22:39 +0200
commitfc792bba0bfaaaeca8a9a1b6ca47c9cd9303d41f (patch)
tree2042fd7846251f5f8dc56343400afbd315dc5377 /behave_tests/features/non-regression.feature
parent8755c892f6cfbfb8ca4f3405675dfe770c769605 (diff)
NFVBENCH-205 - Add behave tests for characterization and non-regression
Change-Id: I708eee21a9fd11e7a276707fb0b43d8598381ce7 Signed-off-by: fmenguy <francoisregis.menguy@orange.com>
Diffstat (limited to 'behave_tests/features/non-regression.feature')
-rw-r--r--behave_tests/features/non-regression.feature48
1 files changed, 48 insertions, 0 deletions
diff --git a/behave_tests/features/non-regression.feature b/behave_tests/features/non-regression.feature
new file mode 100644
index 0000000..5774418
--- /dev/null
+++ b/behave_tests/features/non-regression.feature
@@ -0,0 +1,48 @@
+@non-regression
+Feature: non-regression
+
+ @throughput
+ Scenario Outline: Run a NDR test for a defined frame size
+ Given 10 sec run duration
+ And TRex is restarted
+ And <frame_size> frame size
+ And 100k flow count
+ And ndr rate
+ When NFVbench API is ready
+ Then 3 runs are started and waiting for maximum result
+ And push result to database
+ And extract offered rate result
+ And verify throughput result is in same range as the previous result
+ And verify throughput result is in same range as the characterization result
+
+ Examples: Frame sizes
+ | frame_size |
+ | 64 |
+ | 768 |
+ | 1518 |
+ | 9000 |
+
+
+ @latency
+ Scenario Outline: Run a latency test for a defined frame size and throughput percentage
+ Given 10 sec run duration
+ And TRex is restarted
+ And <frame_size> frame size
+ And 100k flow count
+ And <throughput> rate of previous scenario
+ When NFVbench API is ready
+ Then run is started and waiting for result
+ And push result to database
+ And verify latency result is in same range as the previous result
+ And verify latency result is in same range as the characterization result
+
+ Examples: Frame sizes and throughput percentages
+ | frame_size | throughput |
+ | 64 | 70% |
+ | 64 | 90% |
+ | 768 | 70% |
+ | 768 | 90% |
+ | 1518 | 70% |
+ | 1518 | 90% |
+ | 9000 | 70% |
+ | 9000 | 90% |