Files

Abhishek Kekane 86df53bb05 Add image cache client

Depends-On: https://review.opendev.org/c/openstack/glance/+/842070
Change-Id: Idecb129d0ca96eb44c16f4e682b441a61cab42fb

2022-06-30 07:49:55 +00:00

api

[part1] Remove six

2021-02-24 12:45:22 +00:00

cmd

Remove compute api_extensions config option

2022-05-05 18:15:29 -05:00

common

Introduce PINGABLE and SSHABLE waiters and wait_until state support

2022-03-02 09:21:16 +00:00

files

Change openstack-dev to openstack-discuss

2018-12-04 06:39:07 -05:00

lib

Add image cache client

2022-06-30 07:49:55 +00: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

README.rst

Doc: fix markups, capitalization and add 2 REVIEWING advices

2017-07-11 20:26:32 +02:00

test_base_test.py

Support scope in dynamic cred for specific roles

2021-03-06 17:14:22 +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 compute api_extensions config option

2022-05-05 18:15:29 -05:00

test_hacking.py

Use LOG.warning instead of deprecated LOG.warn

2022-01-19 13:38:21 +09:00

test_imports.py

Use unittest.mock instead of third party mock

2020-05-17 17:22:58 +00:00

test_list_tests.py

[part1] Remove six

2021-02-24 12:45:22 +00:00

test_microversions.py

[part1] Remove six

2021-02-24 12:45:22 +00:00

test_tempest_plugin.py

Add a validation resources fixture

2017-09-12 12:37:24 -06:00

test_test.py

Remove usage of unittest2

2022-01-24 17:49:25 -05: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)