OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|1 month ago|
|doc||7 months ago|
|gabbi_tempest||7 months ago|
|gate/gabbits||7 months ago|
|samples||1 year ago|
|.gitignore||3 years ago|
|.gitreview||1 month ago|
|.zuul.yaml||1 month ago|
|Makefile||1 year ago|
|README.rst||7 months ago|
|requirements.txt||1 year ago|
|setup.cfg||7 months ago|
|setup.py||3 years ago|
|tox.ini||7 months ago|
Gabbi-tempest is a Tempest plugin that enables testing the APIs of running OpenStack services, integrated with tempest but without needing to write Python. Instead the YAML format provided by gabbi is used to write and evaluate HTTP requests and responses.
Tests are placed in YAML files in one or more directories. Those directories are added to a
GABBI_TEMPEST_PATH environment variable. When that variable is passed into a tempest test runner that is aware of the gabbi plugin, the files on that path will be used to create tempests tests.
The test harness sets a series of enviornment variables that can be used in the YAML to reach the available services. The available variables may be extended in two ways:
For each service in the service catalog there are
<SERVICE_TYPE>_BASE variables (e.g.,
PLACEMENT_BASE). A useful
FLAVOR_REF_ALT are also available.
Read the docs at https://gabbi-tempest.readthedocs.io/