openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/tests
History
guo yunxian 7bbbec1ed9 Replace six.iteritems with dict.items 
As [1] mentioned, we should use dict.items instead of six.iteritems.
Let's use dict.items as it should return iterators in PY3 as well.
(As for PY2, the performance about list should be negligible)

[1] https://wiki.openstack.org/wiki/Python3

Change-Id: I77b3a71faa71b5f671daff3415e2ae58289fd3ca
 		2017-01-03 23:17:34 +00:00
..
cmd Define v3 domains_client as library 2016-12-20 12:42:26 +00:00
common Replace six.iteritems with dict.items 2017-01-03 23:17:34 +00:00
files Fix author information 2014-02-24 19:19:22 +09:00
lib Define v3 domains_client as library 2016-12-20 12:42:26 +00:00
negative Remove the Auto Tests Generators 2016-12-07 15:13:42 +01:00
services Replace six.iteritems with dict.items 2017-01-03 23:17:34 +00: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_config.py Revert "Move dscv and ca_certs to config section service_clients" 2016-08-19 14:20:40 +00:00
fake_tempest_plugin.py Service Clients registration interface for plugins 2016-07-26 22:52:33 +01:00
test_base_test.py Stop passing TestResources to Managers 2016-06-09 11:32:22 +01: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 the Stress framework 2016-10-19 14:31:13 +02: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_tempest_plugin.py Only call register_service_clients if there are clients 2016-10-05 11:27:13 -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)