History

Andrea Frittoli d69d1b552b Move multi-nic tests to dedicated module The test_create_server module creates a server and then it runs multiple checks in different tests. This is done for DiskConfig AUTO and MANUAL. The two multinic tests however create their own server, so they should not belong to the same class. With the current setup we run them twice, once per DiskConfig value, which uses gate time and resources for no clear purpose. To fix this I'm moving these two multi nic tests to a dedicated module. Change-Id: I97dd4b5c703d41d9084e6e049144e4df4e3fb75d		2017-07-13 21:54:46 +00:00
..
api	Move multi-nic tests to dedicated module	2017-07-13 21:54:46 +00:00
cmd	Merge "Save state of cloud before running tempest"	2017-07-06 04:20:50 +00:00
common	Update volume-status waiter for new cinder attach	2017-07-03 10:52:05 +02:00
hacking	Add T115 for admin test path	2017-05-23 14:00:27 -07:00
lib	Merge "Add 'params' argument to v2 list_backups API"	2017-07-12 05:50:32 +00:00
scenario	Merge "Boot server from encrypted volume"	2017-07-06 04:48:54 +00:00
services	Fix create, update or delete account metadata method	2017-04-21 02:47:30 +00:00
test_discover	Add docstring example for get_opt_lists	2017-04-24 10:07:39 +00:00
tests	Merge "Add 'params' argument to v2 list_backups API"	2017-07-12 05:50:32 +00:00
README.rst	Remove the Stress framework	2016-10-19 14:31:13 +02:00
__init__.py	…
clients.py	Add test case for update volume backup	2017-07-05 14:46:55 +08:00
config.py	Merge "Pause resource cleanup"	2017-07-05 07:40:05 +00:00
exceptions.py	Move InvalidServiceTag	2017-04-19 11:21:04 +01: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	Merge "Add notes for network and identity in get_service_list"	2017-07-09 13:44:02 +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 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.