Mehdi Abaakouk 57fdce9639 tempest: rework gabbi setup ... The current approach is a bit hacky and create one tempest scenario per gabbi HTTP call. The side effect is that tests continue to run even the previous one have fail. This changes the approach by running gabbi to have one scenario per yaml file from tempest point of view. This will make easier to debug the scenario in case of failure. Change-Id: Ice4be203798a222b4b521540e637fb6ec0c9c01e		2017-05-03 07:43:07 +02:00
..
scenario	tempest: rework gabbi setup	2017-05-03 07:43:07 +02:00
__init__.py	tests: tempest plugin	2016-04-11 21:44:23 +02:00
config.py	Stop adding ServiceAvailable group option	2016-10-03 16:24:18 +05:30
plugin.py	Stop adding ServiceAvailable group option	2016-10-03 16:24:18 +05:30