History

Zuul 4fcc924be8 Merge "Add extra_msg and server parameter to check_vm_connectivity"		2018-07-24 11:16:40 +00:00
..
api	Merge "Skip list FIP test for neutron new behaviour"	2018-07-23 15:14:56 +00:00
cmd	Mark raw strings as such	2018-07-06 14:01:28 +01:00
common	Mark raw strings as such	2018-07-06 14:01:28 +01:00
hacking	Mark raw strings as such	2018-07-06 14:01:28 +01:00
lib	Merge "Omit X-Subject-Token from log"	2018-07-20 05:14:31 +00:00
scenario	Merge "Add extra_msg and server parameter to check_vm_connectivity"	2018-07-24 11:16:40 +00:00
services	Move the object client to tempest.lib	2017-10-17 00:14:20 +00:00
test_discover	Fix doc issue in plugin.py	2017-11-05 21:41:33 +11:00
tests	Add update_service to compute services_client library	2018-07-10 18:56:24 +01:00
README.rst	Fix indentation in README.rst	2018-05-24 08:46:09 +02:00
__init__.py	…
clients.py	Remove volume v2 service client warning	2018-06-07 07:33:49 +00:00
config.py	Remove deprecated allow_tenant_isolation option	2018-07-14 02:16:16 +00:00
exceptions.py	Remove unused RFCViolation	2017-09-11 14:20:20 +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	Fix code to pass pep8 Tox environment.	2018-04-12 11:09:37 +02:00
version.py	…

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