openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/tests
History
Masayuki Igawa d0b8ebd84a
Switch to use stestr for unit tests directly 
This commit switches to use stestr command to run unit tests directly.
Recently, the latest ostestr command uses stestr instead of testr.
However, we should use stestr directly because it's simple and straight
forward. There is no reason to use ostestr for unit tests anymore.

We still have the other ostestr/testr usage such as tempest run command
and documentations. So, that will be changed with following patches.

Change-Id: Iff4abef50178bdc83b868eed4a906e22d790762b
 		2017-09-14 16:00:31 -06:00
..
api Compute images via addClassResourceCleanup 2017-09-13 23:16:46 +00:00
cmd Added unit tests for blacklist and whitelist 2017-08-24 23:02:53 +00:00
common Add a validation resources fixture 2017-09-12 12:37:24 -06:00
files Fix author information 2014-02-24 19:19:22 +09:00
lib Add a validation resources fixture 2017-09-12 12:37:24 -06:00
services Move object storage capabilities_client to lib interface 2017-07-25 01:01:15 +00: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 Fix base unit test class location 2016-04-22 18:11:30 -04:00
fake_config.py Remove some debug print statements 2017-04-19 16:14:26 +02:00
fake_tempest_plugin.py Service Clients registration interface for plugins 2016-07-26 22:52:33 +01:00
test_base_test.py Fix unit test that break isolation 2017-08-18 12:22:26 +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 Move test decorators to common 2017-08-23 17:09:33 +00:00
test_hacking.py Move test decorators to common 2017-08-23 17:09:33 +00:00
test_list_tests.py Switch to use stestr for unit tests directly 2017-09-14 16:00:31 -06: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 Make resource_cleanup stable 2017-09-12 12:37:30 -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)