x/gabbi-tempest
Code Issues Proposed changes
Tempest plugin for automating gabbi-based testing of services.
24 Commits 1 Branch 3 Tags 111 KiB
Python 92.2%
Makefile 7.8%
master
Go to file
OpenDev Sysadmins 4306237126 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.
2019-04-19 19:50:07 +00:00
doc Add rudimentary docs 2018-10-29 14:28:53 +00:00
gabbi_tempest Don't include version information in python 2018-10-29 18:57:22 +00:00
gate/gabbits Provide a gabbi-tempest job, tested by itself 2018-10-26 11:33:50 +01:00
samples Clean up packaging and docs to make this consumable 2018-01-09 17:12:00 +00:00
.gitignore Initial stab and a generic gabbi plugin for tempest 2016-04-08 15:58:31 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:50:07 +00:00
.zuul.yaml OpenDev Migration Patch 2019-04-19 19:50:07 +00:00
Makefile Clean up packaging and docs to make this consumable 2018-01-09 17:12:00 +00:00
README.rst Fix links in README.rst and description mime type 2018-10-29 19:55:38 +00:00
requirements.txt Clean up packaging and docs to make this consumable 2018-01-09 17:12:00 +00:00
setup.cfg Fix links in README.rst and description mime type 2018-10-29 19:55:38 +00:00
setup.py Initial stab and a generic gabbi plugin for tempest 2016-04-08 15:58:31 +00:00
tox.ini Add rudimentary docs 2018-10-29 14:28:53 +00:00

README.rst

Gabbi + Tempest

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:

  • Adding them to the environment that calls tempest if the values are known.
  • Setting them in a subclass of the plugin if the values need to be calculated from what tempest knows.

For each service in the service catalog there are <SERVICE_TYPE>_SERVICE and <SERVICE_TYPE>_BASE variables (e.g., PLACEMENT_SERVICE and PLACEMENT_BASE). A useful SERVICE_TOKEN, IMAGE_REF, FLAVOR_REF and FLAVOR_REF_ALT are also available.

Read the docs at https://gabbi-tempest.readthedocs.io/