History

Matt Riedemann 9968315d43 Conditionally mark test_attach_detach_volume as slow Based on average test times from the last 300 runs of the tempest-full job [1] this change marks the test_attach_detach_volume test as slow but only if SSH validation is enabled, which it is in tempest-full but might not be in other jobs that run it, for example in refstack which uses this test for interoperability certification. [1] http://paste.openstack.org/show/745114/ Change-Id: I47710321d8dfb0345c793e66bd09a5dd1933557b Related-Bug: #1783405		2019-02-15 09:01:30 -05:00
..
api	Conditionally mark test_attach_detach_volume as slow	2019-02-15 09:01:30 -05:00
cmd	Fix tempest cleanup for python3	2019-02-07 14:43:05 +00:00
common	Merge "Ensure volume is deleted after build error"	2019-02-01 09:28:53 +00:00
hacking	Merge "Bump hacking to 1.1.0"	2018-08-21 12:46:22 +00:00
lib	Allow decorators.attr to be conditional	2019-02-15 09:01:26 -05:00
scenario	Mark test_server_connectivity_reboot as slow	2019-02-14 14:09:11 -05: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	Allow decorators.attr to be conditional	2019-02-15 09:01:26 -05:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	[Trivial fix]Remove unnecessary slash	2019-01-10 10:43:16 +08:00
config.py	Merge "fix port_profile"	2019-02-06 05:51:45 +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	docs: Fix incorrect docstrings in reStructuredText format	2018-11-21 19:06:43 -06: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.