History

Zuul fa5e69d455 Merge "Add prefix to images created in *ImagesNegativeTest tests"		2024-03-06 03:46:00 +00:00
..
api	Merge "Add prefix to images created in *ImagesNegativeTest tests"	2024-03-06 03:46:00 +00:00
cmd	Add '--slowest' option to 'tempest run'	2023-12-07 03:35:55 +00:00
common	Add delete image from specific store API	2023-12-13 09:42:28 +02:00
hacking	Use LOG.warning instead of deprecated LOG.warn	2022-01-19 13:38:21 +09:00
lib	cli auth: only inject project name if provided	2024-02-10 15:51:07 -08:00
scenario	Merge "Add option to specify source and destination host"	2024-02-28 21:03:16 +00:00
serial_tests	General doc updates	2024-01-31 09:00:16 +01:00
test_discover	Introduce @serial test execution decorator	2023-01-18 02:45:43 +00:00
tests	Merge "Add '--slowest' option to 'tempest run'"	2024-02-08 20:28:08 +00:00
README.rst	General doc updates	2024-01-31 09:00:16 +01:00
__init__.py	…
clients.py	Add coverage for caching image on remote node	2024-03-04 15:04:53 +00:00
config.py	Merge "Add option to specify source and destination host"	2024-02-28 21:03:16 +00:00
exceptions.py	Break wait_for_volume_resource_status when error_extending	2019-06-03 15:37:13 +08:00
test.py	Fail create if validation flags do not agree	2023-05-02 13:09:23 -07: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 its 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
   serial_tests/ - tests that run always in the serial mode
   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 a 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.

`serial_tests_guide`

Tests within this category will always be executed serially from the rest of the test cases.

`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.