openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/tests
History
Yaroslav Lobankov db4a2e162f Changing directory structure for Cinder clients 
The tempest/services/volume directory had the following structure:

        tempest
        |___services
            |___volume
                |____json
                |    |____admin
                |    |    |____<client files>
                |    |
                |    |____<client files>
                |
                |____v2
                     |____json
                          |____admin
                          |    |____<client files>
                          |
                          |____<client files>

The structure was changed to keep consistency with other clients directories.
For example, the tempest/services/identity derectory and the tempest/services/image
directory. So now the structure is the following:

        tempest
        |___services
            |___volume
                |____base
                |    |____<client files>
                |
                |____v1
                |    |____json
                |         |____admin
                |         |    |____<client files>
                |         |
                |         |____<client files>
                |
                |____v2
                     |____json
                          |____admin
                          |    |____<client files>
                          |
                          |____<client files>

The tempest/services/volume/base directory was created and now it containes base
client files with base client classes for v1 and v2 Cinder clients.

Change-Id: I0ac37e15eddffb12d150dcd5b68e0f933712d22c
 		2015-12-01 12:01:43 +03:00
..
cmd Move get_user_by_username to common part 2015-11-19 06:10:21 +00:00
common Changing directory structure for Cinder clients 2015-12-01 12:01:43 +03:00
files Fix author information 2014-02-24 19:19:22 +09:00
negative Switch all uses of iteritems to use six instead 2015-05-10 12:46:22 -04:00
services Use tenant_usages_client from tempest-lib 2015-11-25 17:15:46 +09:00
stress Fix H404/405 violations for unit tests 2015-11-19 08:45:06 +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 H404/405 violations for unit tests 2015-11-19 08:45:06 +00: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 credential config options 2015-09-10 11:05:23 -04:00
fake_http.py Fix H404/405 violations for unit tests 2015-11-19 08:45:06 +00:00
fake_identity.py Switch all uses of json to oslo_serialization 2015-07-14 11:14:29 -04:00
fake_tempest_plugin.py Add initial unit test for tempest plugins 2015-08-28 10:16:43 +02:00
test_decorators.py Unbreak the world! 2015-06-29 16:35:43 -04:00
test_glance_http.py Switch all uses of json to oslo_serialization 2015-07-14 11:14:29 -04:00
test_hacking.py Fix H404/405 violations for unit tests 2015-11-19 08:45:06 +00:00
test_list_tests.py Fix last unit tests on py34 2015-05-12 18:58:00 +00:00
test_negative_rest_client.py Separate tests of negative_rest_client 2015-01-13 00:38:08 +00:00
test_tempest_plugin.py Add initial unit test for tempest plugins 2015-08-28 10:16:43 +02:00
test_wrappers.py Switch all uses of StringIO to use it from six 2015-04-23 12:00:05 -04: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)