History

Zuul 8f3e503413 Merge "Adding description for testcases - compute part1"		2020-04-15 08:19:01 +00:00
..
api	Merge "Adding description for testcases - compute part1"	2020-04-15 08:19:01 +00:00
cmd	Merge "Fix deletion of network quotas"	2020-04-13 17:01:14 +00:00
common	Merge "Support force-deletion of servers."	2020-04-03 20:19:09 +00:00
hacking	Update hacking for Python3	2020-04-04 10:33:23 +02:00
lib	Update hacking for Python3	2020-04-04 10:33:23 +02:00
scenario	Explicitly handle baremetal ports when checking if they are active	2020-04-14 17:10:20 +02:00
services	Move the object client to tempest.lib	2017-10-17 00:14:20 +00:00
test_discover	Add autopep8 to tox.ini	2019-03-08 16:04:05 +01:00
tests	Merge "add unittest for create and list resource types association"	2020-04-09 11:40:14 +00:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	services: Introduce a cinder v3 attachments client	2020-03-02 09:02:50 +00:00
config.py	Add subnet_id option	2020-03-18 10:15:55 +00:00
exceptions.py	Break wait_for_volume_resource_status when error_extending	2019-06-03 15:37:13 +08:00
manager.py	Merge "Revert "Move dscv and ca_certs to config section service_clients""	2016-08-20 22:48:10 +00:00
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.