openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/tests
History
Masayuki Igawa ce7c69673a Add unit test for data_utils 
This commit adds data_utils except build_url function because of no user
for that function.

Note: Removing build_url function is another topic. So the patch is
separated: I8989ac12f36f342ca1066cc65f7a427a83de721f .

Partially implements bp unit-tests

Change-Id: I1e3b3c4916144fe82c5708a6c30fe94a3d1c5e58
 		2014-03-10 16:23:16 +09:00
..
common Add unit test for data_utils 2014-03-10 16:23:16 +09:00
files Fix author information 2014-02-24 19:19:22 +09:00
negative Add multiple negative test generator support 2014-03-06 08:21:28 +01:00
stress Remove vim headers 2014-01-20 11:22:45 +09:00
README.rst Add 'Field' to the title of the Field Guides 2013-09-18 13:29:53 +09:00
__init__.py Add unittest framework + tests for wrapper scripts 2013-08-27 11:55:13 -04:00
base.py Merge "Add unit tests for SSH client functionality" 2014-01-25 19:27:41 +00:00
fake_auth_provider.py Multiversion authentication part1 2014-02-05 11:34:53 +00:00
fake_config.py Add multiple negative test generator support 2014-03-06 08:21:28 +01:00
fake_http.py Add unit tests to tempest auth file 2014-02-24 19:28:38 +00:00
fake_identity.py Improve tempest auth tests 2014-02-26 08:14:52 -05:00
test_auth.py Improve tempest auth tests 2014-02-26 08:14:52 -05:00
test_compute_xml_common.py Add bool and integer support to XML parser 2014-01-30 14:15:00 +04:00
test_decorators.py Mildly wound the interlopers 2014-02-19 16:17:32 +00:00
test_list_tests.py Remove vim headers 2014-01-20 11:22:45 +09:00
test_rest_client.py Use Python 2.6.x compatible syntax for dict comprehension 2014-02-21 15:48:32 +01:00
test_ssh.py Add log info for tempest SSH connection issues 2014-02-03 11:31:36 -05:00
test_wrappers.py stop leaking tempdirs 2014-01-30 16:08:41 -05: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)