Tempest plugin for automating gabbi-based testing of services.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 4306237126 OpenDev Migration Patch 1 month ago
doc Add rudimentary docs 6 months ago
gabbi_tempest Don't include version information in python 6 months ago
gate/gabbits Provide a gabbi-tempest job, tested by itself 6 months ago
samples Clean up packaging and docs to make this consumable 1 year ago
.gitignore Initial stab and a generic gabbi plugin for tempest 3 years ago
.gitreview OpenDev Migration Patch 1 month ago
.zuul.yaml OpenDev Migration Patch 1 month ago
Makefile Clean up packaging and docs to make this consumable 1 year ago
README.rst Fix links in README.rst and description mime type 6 months ago
requirements.txt Clean up packaging and docs to make this consumable 1 year ago
setup.cfg Fix links in README.rst and description mime type 6 months ago
setup.py Initial stab and a generic gabbi plugin for tempest 3 years ago
tox.ini Add rudimentary docs 6 months ago

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/