tempest/tempest
zhufl 0ea2c01d75 Break wait_for_volume_resource_status when error_extending
When extending volume reaches status error_extending, we should
return from wait_for_volume_resource_status immediately instead
of waiting for the TimeoutException.

Change-Id: I3db0325c23ebb8d42fe77f4c28552fe9cf5ed807
2019-06-03 15:37:13 +08:00
..
api Merge "Add APIMicroversionFixture to library interface" 2019-05-28 18:22:07 +00:00
cmd Improve router deletion logging in tempest cleanup 2019-04-02 12:51:44 +00:00
common Break wait_for_volume_resource_status when error_extending 2019-06-03 15:37:13 +08:00
hacking Merge "Bump hacking to 1.1.0" 2018-08-21 12:46:22 +00:00
lib Merge "Add APIMicroversionFixture to library interface" 2019-05-28 18:22:07 +00:00
scenario Merge "Improve ipv6 configuration" 2019-05-29 21:45:16 +00: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 Break wait_for_volume_resource_status when error_extending 2019-06-03 15:37:13 +08: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 "Adds protocol options for test_cross_tenant_traffic" 2019-05-29 21:44:37 +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 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.