c0348ee84e
This patchset adds update_service to compute module's services_client library. This API is introduced in microversion 2.53 and supersedes the following APIs: * ``PUT /os-services/disable`` (``disable_service``) * ``PUT /os-services/disable-log-reason`` (``disable_log_reason``) * ``PUT /os-services/enable`` (``enable_service``) * ``PUT /os-services/force-down`` (``update_forced_down``) Negative tests were added for all the APIs above. The negative tests only test the microversion >= 2.53 case: the new udpate_service API is called (also with bad parameters). The v2_11 schema was updated to reference all the unchanged APIs from v2_1 for the compute services api_schema. Also, the v2_53 schema was introduced for the new update_service API and it also references all the unchanged APIs from v2_1. Finally, unit tests and releasenotes are included. Change-Id: I5e7b81496cbb87cda81413124b5f82bd5356e666 |
||
---|---|---|
.. | ||
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)