OpenStack Testing (Tempest) of an existing cloud
433dbdc4b9
This patch proposes adding several new unit tests in effort to increase the total unit test coverage. Additionally, the ./tempest/serial_tests/ directory is not included in coverage calculation. The reason being we don't want to test tests with unit tests, which becomes a bit of an overkill. Finally, there is an addition of a new option for the coverage program called --fail-under. It will result the program in failure if the coverage is under set percentage. Reason for this implementation is to encourage writing unit tests for new code. Change-Id: I804116413cd7d73cd7e5ae71409a8855ef937b88 |
||
---|---|---|
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.