History

Benny Kopilov f5e277c802 Add wait_for_resource_deletion for swift api clients Currently today we dont have any way in swift to verify that resources were deleted before moving to the next command In current code there was hardcoded sleep for 2 seconds instead of checking if resource really deleted. Added to the current cleanup : Implement is_resource_deleted for object_client and container_client After remove action we wait/ verify till resource really deleted Remove hardcoded sleep for 2 seconds Remove ignore for not found in reomval , if we hit on it means something wrong in our code. Change-Id: I32f37f8e874a3510bb1af6db45a1b9a8d2fed543		2021-02-08 16:22:38 +02:00
..
api	Add wait_for_resource_deletion for swift api clients	2021-02-08 16:22:38 +02:00
cmd	Merge "Remove six.PY3/six.PY2"	2020-11-27 01:52:40 +00:00
common	Merge "Move horizon test from tempest-horizon to tempest"	2021-01-22 17:08:10 +00:00
hacking	Update hacking for Python3	2020-04-04 10:33:23 +02:00
lib	Add wait_for_resource_deletion for swift api clients	2021-02-08 16:22:38 +02:00
scenario	Make _log_console_output non-private	2021-02-04 22:05:57 +05:30
services	Move the object client to tempest.lib	2017-10-17 00:14:20 +00:00
test_discover	Use os.path.join as possible	2020-09-06 09:49:40 +00:00
tests	Merge "Add client methods and tests for system grants"	2021-01-22 04:44:35 +00:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	Add placement API methods for testing routed provider nets	2020-09-28 06:45:37 +00:00
config.py	Merge "Move horizon test from tempest-horizon to tempest"	2021-01-22 17:08:10 +00:00
exceptions.py	Break wait_for_volume_resource_status when error_extending	2019-06-03 15:37:13 +08:00
manager.py	Need to have stable tempest scenario manager	2020-09-03 15:49:53 +05:30
test.py	Add workaround to handle the testtool skip exception in CLI test	2019-10-12 01:40:29 +00:00
version.py	Add reno to tempest	2016-02-24 11:31:32 -05:00

README.rst

Tempest Field Guide Overview

Tempest is designed to be useful for a large number of different environments. This includes being useful for gating commits to OpenStack core projects, being used to validate OpenStack cloud implementations for both correctness, as well as a burn in tool for OpenStack clouds.

As such Tempest tests come in many flavors, each with their own rules and guidelines. Below is the overview of the Tempest repository structure to make this clear.

tempest/
   api/ - API tests
   scenario/ - complex scenario tests
   tests/ - unit tests for Tempest internals

Each of these directories contains different types of tests. What belongs in each directory, the rules and examples for good tests, are documented in a README.rst file in the directory.

`api_field_guide`

API tests are validation tests for the OpenStack API. They should not use the existing Python clients for OpenStack, but should instead use the Tempest implementations of clients. Having raw clients let us pass invalid JSON to the APIs and see the results, something we could not get with the native clients.

When it makes sense, API testing should be moved closer to the projects themselves, possibly as functional tests in their unit test frameworks.

`scenario_field_guide`

Scenario tests are complex "through path" tests for OpenStack functionality. They are typically a series of steps where complicated state requiring multiple services is set up exercised, and torn down.

Scenario tests should not use the existing Python clients for OpenStack, but should instead use the Tempest implementations of clients.

`unit_tests_field_guide`

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.