ead5d0d51a
Previously, the host was the endpoint of the service being tested. This is limiting if what's really desired is testing multiple services. So now we move towards setting environmen variable that are the endpoints for any of the services that are going to be used. Then these can be made available from any test. Right now it is not like that. Right now it builds environments based on the requested types. Better to just set them all and then allow the host either be a primary service type endpoint, or a stub if it really is going to be lots. Committing now because tests are mostly passing (except for the phantom failures). Cleanup to come. |
||
---|---|---|
gabbi_tempest | ||
.gitignore | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py |
README.rst
Gabbi + Tempest
This is an exploration of running gabbi as a tempest plugin. This code is based entirely on the work of Mehdi Abaakouk who made a tempest plugin for gnocchi. This code models that but will try to be more generic, eventually.
For the time being it works with Nova.
To experiment with it you need a working tempest installation and configuration. I used devstack with:
enable_service tempest
in local.conf.
Once tempest is confirmed to be working, make a clone of this repo, cd into it and do the equivalent of:
pip install -e .
If you are using virtualenvs or need sudo, your form will be different.
Go to the tempest directory and run testr limit the test run to gabbi related tests:
testr run gabbi --subunit |subunit-trace
This will run the tests described by the YAML files in
gabbi_tempest/tests/scenario/gabbits/
. Edit those files and
run the testr command again for fun and adventure.