7729380f83
When an API server is on an unversioned path (for example, keystone is on http://localhost/identity), verify-config would fail with a 404 Not Found because the version wasn't put on the URL as required (for example, the v2.0 keystone url should have been http://localhost/identity/v2.0 but was instead http://localhost/identity). This is because the version replacement code wasn't adding the version when it wasn't present and a path was there. Change-Id: I559bd967a87b646906f37df81a7db096148488db |
||
---|---|---|
.. | ||
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_base_test.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)