History

Lee Yarwood e5597401ff Introduce an attached volume migration test This change introduces a true cinder host to host attached volume migration test in addition to the existing attached volume retype test. To enable this two new calls are introduced to the v3 volume client to allow all volume backends to be listed per project and to also call for a direct volume migration between backends. Related-bug: #1803961 Depends-On: I1bdf3431bda2da98380e0dcaa9f952e6768ca3af Change-Id: I501eb0cd5eb101b4dc553c2cdbc414693dd5b681		2019-04-25 10:34:58 +01:00
..
api	Merge "Fix invalid filter passed to list_volumes"	2019-04-18 17:32:48 +00:00
cmd	Improve router deletion logging in tempest cleanup	2019-04-02 12:51:44 +00:00
common	Introduce an attached volume migration test	2019-04-25 10:34:58 +01:00
hacking	Merge "Bump hacking to 1.1.0"	2018-08-21 12:46:22 +00:00
lib	Introduce an attached volume migration test	2019-04-25 10:34:58 +01:00
scenario	Introduce an attached volume migration test	2019-04-25 10:34:58 +01: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	Introduce an attached volume migration test	2019-04-25 10:34:58 +01:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	Init placement client in tempest Manager object	2019-04-01 09:35:42 -04:00
config.py	Merge "Add profiler support into Tempest"	2019-03-17 21:46:15 +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	Add profiler support into Tempest	2019-02-16 08:10:28 +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.