ceb882169a
The goal of this placement client for tempest is to make possible the end-to-end testing of the placement based bandwidth feature (see the nova and neutron specs: https://review.openstack.org/502306 https://review.openstack.org/508149) The minimum placement microversion is 1.29, and the following operations are supported: list_allocation_candidates, list_allocations. Change-Id: I0cf1caadeb40761ec79338510919f12baf2d8f56 Partial-Bug: #1578989 See-Also: https://review.openstack.org/502306 (nova spec) See-Also: https://review.openstack.org/508149 (neutron spec) |
||
---|---|---|
.. | ||
api | ||
cmd | ||
common | ||
files | ||
lib | ||
README.rst | ||
__init__.py | ||
base.py | ||
fake_config.py | ||
fake_tempest_plugin.py | ||
test_base_test.py | ||
test_config.py | ||
test_decorators.py | ||
test_hacking.py | ||
test_imports.py | ||
test_list_tests.py | ||
test_microversions.py | ||
test_tempest_plugin.py | ||
test_test.py | ||
utils.py |
README.rst
Tempest Field Guide to Unit tests
What are these tests?
Unit tests are the self checks for Tempest. They provide functional verification and regression checking for the internal components of Tempest. They should be used to just verify that the individual pieces of Tempest are working as expected. They should not require an external service to be running and should be able to run solely from the Tempest tree.
Why are these tests in Tempest?
These tests exist to make sure that the mechanisms that we use inside of Tempest are valid and remain functional. They are only here for self validation of Tempest.
Scope of these tests
Unit tests should not require an external service to be running or any extra configuration to run. Any state that is required for a test should either be mocked out or created in a temporary test directory. (see test_wrappers.py for an example of using a temporary test directory)