cad3f3d834
This was a backwards incompatible change that breaks tempest's stability
guarantee on tempest.config. While the option was marked as deprecated,
oslo.config does not alias deprecations in code. The fact this patch
had to update unit tests was an indication of this. This breaks anyone
who consumes these options via code. We can only land something like
this after we add aliasing to oslo.config for deprecations.
This reverts commit
|
||
---|---|---|
.. | ||
cmd | ||
common | ||
files | ||
lib | ||
negative | ||
services | ||
stress | ||
__init__.py | ||
base.py | ||
fake_auth_provider.py | ||
fake_config.py | ||
fake_tempest_plugin.py | ||
README.rst | ||
test_base_test.py | ||
test_config.py | ||
test_decorators.py | ||
test_hacking.py | ||
test_list_tests.py | ||
test_microversions.py | ||
test_negative_rest_client.py | ||
test_tempest_plugin.py | ||
test_wrappers.py | ||
utils.py |
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 to 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)