tempest/tempest/tests
Matthew Treinish ffad78a29f
Fix base unit test class location
The recent commit I45d73891f3c0829a2378a032dfc02e5ac0ee34b7
deduplicated the base test class methods from the tempest.lib
reintegration. However the surviving base class was put in the wrong
namespace. The base class is just that a base to build the individual
test subclass off of. It's very confusing for that to not live in the
base tests namespace. While the code in lib is supposed to be self
contained there isn't a reason to do that here for the unit tests,
especially because in this case the import heiarchy becomes more
confusing with the base living in a submodule. This commit moves the
base class to the base tempest.tests namespace where it really
belongs.

Change-Id: I079eeb1135eed3254e5e9dbebac8a52b979303c7
2016-04-22 18:11:30 -04:00
..
cmd Fix base unit test class location 2016-04-22 18:11:30 -04:00
common Fix base unit test class location 2016-04-22 18:11:30 -04:00
files Fix author information 2014-02-24 19:19:22 +09:00
lib Fix base unit test class location 2016-04-22 18:11:30 -04:00
negative Fix base unit test class location 2016-04-22 18:11:30 -04:00
services Move keypair client to lib interfaces 2016-04-07 00:42:26 +00:00
stress Fix base unit test class location 2016-04-22 18:11:30 -04:00
README.rst Add unit test section to the field guide index 2014-07-25 16:13:10 -04:00
__init__.py Add unittest framework + tests for wrapper scripts 2013-08-27 11:55:13 -04:00
base.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
fake_auth_provider.py Move fake get_credentials methods to test_auth 2015-01-15 07:17:17 +00:00
fake_config.py deprecate use of tenant in configs 2016-04-06 22:26:18 +01:00
fake_tempest_plugin.py Add initial unit test for tempest plugins 2015-08-28 10:16:43 +02:00
test_base_test.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
test_decorators.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
test_glance_http.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
test_hacking.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
test_list_tests.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
test_microversions.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
test_negative_rest_client.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
test_tempest_plugin.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
test_wrappers.py Fix base unit test class location 2016-04-22 18:11:30 -04:00
utils.py Unit tests: mock some time.sleep and time.time 2016-03-03 14:33:45 +01:00

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)