See: https://pagure.io/fedora-ci/general/issue/11

1) Extend the tests.yaml definition to declare that each test needs a fresh test bed.

• convenient for tests as they don't have to do any setup, and might be good enough for most use cases
• does not work well with running tests locally, as the test invocation interface is currently all around Ansible, which does not have this concept of building/controlling targets
• not very flexible, as e. g. tests still cannot reboot the test bed

@mvadkert : Having some implementation of 1) would definitively help for us to be able to run more than one integration test.

It would be very inefficient, as setup steps (like downloading and setting up selenium etc. containers) or intalling test dependencies into the VM cannot be shared, and need to be re-done for every test case. In our case, the setup takes pretty much the entire time (magnitude of 10 minutes), while the actual test only takes very few seconds. So this inefficiency is certainly not negligible.