openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/tests
History
Tomas Krchnak 536d8284f4 Add unit tests for check_uuid.py 
* adding a patch
* applying a patch
* adding uuid to test - with and without decorator
* adding import line to tests with uuid

Closes-Bug: #1878171

Change-Id: I59e2cb3bd0ee9a8b525b5904fd39eba446205efd
 		2020-06-24 15:03:08 +00:00
..
api Use unittest.mock instead of third party mock 2020-05-17 17:22:58 +00:00
cmd Fix the argument check for account-generator 2020-06-15 07:03:34 +00:00
common Use unittest.mock instead of third party mock 2020-05-17 17:22:58 +00:00
files Change openstack-dev to openstack-discuss 2018-12-04 06:39:07 -05:00
lib Add unit tests for check_uuid.py 2020-06-24 15:03:08 +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 Use unittest.mock instead of third party mock 2020-05-17 17:22:58 +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 Use unittest.mock instead of third party mock 2020-05-17 17:22:58 +00: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 Update hacking for Python3 2020-04-04 10:33:23 +02:00
test_imports.py Use unittest.mock instead of third party mock 2020-05-17 17:22:58 +00: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 Use unittest.mock instead of third party mock 2020-05-17 17:22:58 +00: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)