openstack/tempest
Code Issues Proposed changes
926f823fbd
tempest/tempest/tests
History
Rao Adnan Khan ac1aaf6624 Add client for assisted volume snapshots API. 
This will invoke post and delete calls on os-assisted-volume-snapshots
endpoint.

Closes-bug: #1668407

Co-Authored-By: Ghanshyam Mann <gmann@ghanshyammann.com>

Change-Id: I81e8fd9f89ec1cb00fc0116c31f9c0559406164
2021-03-23 17:04:50 -05:00
..
api [part1] Remove six 2021-02-24 12:45:22 +00:00
cmd Fix test_verify_tempest_config unit tests 2021-03-10 10:30:25 +00:00
common Merge "Remove usage of six" 2021-02-19 20:02:01 +00:00
files Change openstack-dev to openstack-discuss 2018-12-04 06:39:07 -05:00
lib Add client for assisted volume snapshots API. 2021-03-23 17:04:50 -05: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 deprecated test.idempotent_id decorator 2021-01-06 17:35:39 +00: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 [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 Support scope in dynamic cred for specific roles 2021-03-06 17:14:22 +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)