History

inspurericzhang f70df52fda [Trivial Fix] modify spelling error of "resource" Although it is spelling mistakes, it affects reading. Change-Id: I690b0d831f63b5e2b7bbaf6d9cdc18ae834ce3fb		2018-11-01 09:44:14 +08:00
..
api	Set max_microversion 2.35 for nova image tests	2018-07-27 16:15:30 +08:00
cmd	Merge "Adding missing test cases in "test_run.py""	2018-10-31 07:13:34 +00:00
common	Mark raw strings as such	2018-07-06 14:01:28 +01:00
files	update the home-page url	2018-02-26 01:46:51 +00:00
lib	[Trivial Fix] modify spelling error of "resource"	2018-11-01 09:44:14 +08:00
README.rst	Doc: fix markups, capitalization and add 2 REVIEWING advices	2017-07-11 20:26:32 +02:00
__init__.py	Add unittest framework + tests for wrapper scripts	2013-08-27 11:55:13 -04:00
base.py	Improve patch and patchobject Base test case method attributes.	2018-04-10 11:07:30 +00:00
fake_config.py	Add test coverage CMD cleanup_service	2018-09-27 17:02:18 +00:00
fake_tempest_plugin.py	Service Clients registration interface for plugins	2016-07-26 22:52:33 +01:00
test_base_test.py	Default to using neutron networks_client in get_tenant_network	2018-01-11 17:46:08 +08:00
test_config.py	Revert "Move dscv and ca_certs to config section service_clients"	2016-08-19 14:20:40 +00:00
test_decorators.py	Remove deprecated skip decorators	2017-09-21 17:17:07 +08:00
test_hacking.py	Hacking checks for negative test cases	2018-07-28 21:43:45 -04:00
test_imports.py	Add unit tests to check for CONF getattr during import	2017-10-26 18:08:51 -04:00
test_list_tests.py	Mark raw strings as such	2018-07-06 14:01:28 +01:00
test_microversions.py	Unsupported 'message' Exception attribute in PY3	2017-07-31 07:30:28 +00:00
test_tempest_plugin.py	Add a validation resources fixture	2017-09-12 12:37:24 -06:00
test_test.py	Add unit tests for not overriding setUpClass	2017-09-14 13:00:31 -06: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 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)