History

Jenkins e0ef05ce0d Merge "Move oslo config generator config inside package"		2016-06-23 11:23:50 +00:00
..
cmd	Merge "Move oslo config generator config inside package"	2016-06-23 11:23:50 +00:00
common	Merge "Change hostname_equals_servername to get_hostname"	2016-06-21 10:07:21 +00:00
files	Fix author information	2014-02-24 19:19:22 +09:00
lib	Remove unnecessary setUp and tearDown	2016-06-23 10:34:42 +08:00
negative	Fix base unit test class location	2016-04-22 18:11:30 -04:00
services	Return ResponseBody object from delete_role	2016-06-17 18:54:16 +09: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	Addresses Expect: 100-continue client behavior	2016-05-11 09:33:10 -05:00
fake_config.py	Remove deprecated legacy credentials provider	2016-05-20 18:32:15 -04:00
fake_tempest_plugin.py	Add initial unit test for tempest plugins	2015-08-28 10:16:43 +02:00
test_base_test.py	Stop passing TestResources to Managers	2016-06-09 11:32:22 +01:00
test_decorators.py	Add test case for CONF skip decorators with message	2016-05-10 14:27:36 +09:00
test_hacking.py	Add hacking rule to enfore no config in tempest.lib	2016-06-01 15:05:59 -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)