tree e2eccdd78b2b0531e231040e5cf7c1e05154c9f1
parent fca71e43a076d8d684e226e65828714c0300dd23
author Mehdi Abaakouk <sileht@redhat.com> 1490198991 +0100
committer Mehdi Abaakouk <sileht@redhat.com> 1492505640 +0200

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: I594288322d9ac5d3d128d601cba1d2291a632e20