History

Benny Kopilov 8a33ee1117 Fix volume_create to use shared function with a cleanup delete volume is taken care by self.create_volume Change-Id: Ic4cb5dae7a7165d28df3cab97019c1756a70dfbf		2016-11-15 19:15:21 +00:00
..
api	Fix volume_create to use shared function with a cleanup	2016-11-15 19:15:21 +00:00
cmd	Merge "Remove the Stress framework"	2016-10-24 13:02:43 +00:00
common	Fix volume_create to use shared function with a cleanup	2016-11-15 19:15:21 +00:00
hacking	Delete Savanna element in client list	2016-09-21 03:00:15 +00:00
lib	Merge "Update volume client class description"	2016-11-08 08:19:20 +00:00
scenario	Merge "Get rid of useless tenant_id attribiute"	2016-11-09 08:07:23 +00:00
services	Merge "Delete TimeoutException in tempest/exceptions.py"	2016-11-04 15:00:16 +00:00
test_discover	Only call register_service_clients if there are clients	2016-10-05 11:27:13 -04:00
tests	Merge "Correct a scheme example error from fake netutron versions client"	2016-11-08 12:57:42 +00:00
README.rst	Remove the Stress framework	2016-10-19 14:31:13 +02:00
__init__.py	…
clients.py	Fix cinder message-client naming to volume_v3_messages_client	2016-11-03 15:45:32 +02:00
config.py	Remove the Stress framework	2016-10-19 14:31:13 +02:00
exceptions.py	Delete TimeoutException in tempest/exceptions.py	2016-11-03 09:52:18 +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	Move cred_client to tempest.lib	2016-11-07 10:03:27 -05: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 proposed Havana restructuring for Tempest to make this clear.

tempest/
api/ - API tests
scenario/ - complex scenario tests

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.