80369a96a2
data_utils.rand_name() appends randam charactors with a hypen like: def rand_name(name=''): randbits = str(random.randint(1, 0x7fffffff)) if name: return name + '-' + randbits So it is not necessary to specify a hypen in caller side. This patch adds a hacking rule for blocking "-" at the end of argument of rand_name() calls. Change-Id: I9b9f25dbe5a3ef5ac5900113bcc46e0d911becc9 |
||
---|---|---|
.. | ||
cmd | ||
common | ||
files | ||
negative | ||
stress | ||
README.rst | ||
__init__.py | ||
base.py | ||
fake_auth_provider.py | ||
fake_config.py | ||
fake_http.py | ||
fake_identity.py | ||
test_decorators.py | ||
test_glance_http.py | ||
test_hacking.py | ||
test_list_tests.py | ||
test_negative_rest_client.py | ||
test_tenant_isolation.py | ||
test_waiters.py | ||
test_wrappers.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)