When extending volume reaches status error_extending, we should return from wait_for_volume_resource_status immediately instead of waiting for the TimeoutException. Change-Id: I3db0325c23ebb8d42fe77f4c28552fe9cf5ed807
|4 years ago|
|api||5 years ago|
|cmd||4 years ago|
|common||4 years ago|
|files||4 years ago|
|lib||4 years ago|
|README.rst||6 years ago|
|__init__.py||10 years ago|
|base.py||5 years ago|
|fake_config.py||5 years ago|
|fake_tempest_plugin.py||7 years ago|
|test_base_test.py||5 years ago|
|test_config.py||7 years ago|
|test_decorators.py||6 years ago|
|test_hacking.py||4 years ago|
|test_imports.py||6 years ago|
|test_list_tests.py||5 years ago|
|test_microversions.py||6 years ago|
|test_tempest_plugin.py||6 years ago|
|test_test.py||6 years ago|
|utils.py||7 years ago|
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)