OpenStack Testing (Tempest) of an existing cloud
![]() Zuul can do better resource allocation if it learns early that a job will fail even when tests haven't completed yet. This is done by adding a regular expression that will match on a single failing test within a tempest run. The regex is copied from what the zuul project has already been using successfully for some time. Change-Id: I8c9488a55d04e32384d1523a9658a8711b05c340 |
||
---|---|---|
doc | ||
etc | ||
playbooks | ||
releasenotes | ||
roles | ||
tempest | ||
tools | ||
zuul.d | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
REVIEWING.rst | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Team and repository tags
Tempest - The OpenStack Integration Test Suite
This is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, scenarios, and other specific tests useful in validating an OpenStack deployment.
- Documentation: https://docs.openstack.org/tempest/latest/
- Features: https://specs.openstack.org/openstack/qa-specs/#tempest
- Bugs: https://bugs.launchpad.net/tempest/
- Release Notes: https://docs.openstack.org/releasenotes/tempest
Get in touch via email. Use [tempest] in your subject.