OpenStack Testing (Tempest) of an existing cloud
5b36c36896
If first image is not captured in saving state, then we should skip the test - test_create_second_image_when_first_image_is_being_saved Test is for creating the another image is first one is in saving state and if image creation operation is fast and it gets created before second API request then this test will fail on its assert. To handle the test scope and this race condition, we need to assert on second operation if image is in saving state.This can be done via capturing the timeout exception from first image creation and waiting for saving state. Change-Id: Id59f7ebb223f968109917182e29267faa808a072 Closes-Bug: #1881592 |
||
---|---|---|
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.