Add "Scenario" class wait methods for runners 71/53571/8
authorRodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
Mon, 12 Mar 2018 14:14:57 +0000 (14:14 +0000)
committerRodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
Wed, 21 Mar 2018 09:15:44 +0000 (09:15 +0000)
commitbf892d9cf62b6bc64ea76d8b69a8fe3751cabd75
treebbdfc7be2b8888cc6c0c5f6a5381720253e74548
parentc17d65bc5f620328079a6905ebcdd73138685d5f
Add "Scenario" class wait methods for runners

"Duration" and "Iteration" runners execute a passive wait during the
execution of the work process. This wait time is done at the end of
the scenario "run" method execution.

This patch adds a pre-run and post-run wait period, which will
depends on the Scenario executed. The wait time will be always the
same, but the execution order (pre-wait time, run method, post-wait
time) will depends on the Scenario.

By default, any Scenario will execute the "run" method and them will
wait the specified time.

NetworkServicesTestCase Scenario will wait the specified time and them
will execute the "run" method to retrieve the KPIs.

JIRA: YARDSTICK-1067

Change-Id: I6ad6bfc6978815b6b2d4df63f2ac2f8815fb5b8a
Signed-off-by: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
yardstick/benchmark/runners/duration.py
yardstick/benchmark/runners/iteration.py
yardstick/benchmark/scenarios/base.py
yardstick/benchmark/scenarios/networking/vnf_generic.py
yardstick/tests/unit/benchmark/scenarios/test_base.py