0e53b61f85
Similar to what Cinder did here [1], this patch mocks time.sleep to make tests run faster. Some code actually measure the wall clock to wait for a specific duration before raising a TimeoutError, so we also need to mock time.time. This removes ~5sec in unit test and also removes some busy waiting. [1] https://review.openstack.org/#/c/285658/ Change-Id: I69ba35eff591a5df28049273f3aba15c31f52d00 |
||
---|---|---|
.. | ||
cmd | ||
common | ||
files | ||
lib | ||
negative | ||
services | ||
stress | ||
README.rst | ||
__init__.py | ||
base.py | ||
fake_auth_provider.py | ||
fake_config.py | ||
fake_http.py | ||
fake_identity.py | ||
fake_tempest_plugin.py | ||
test_decorators.py | ||
test_glance_http.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 |
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 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)