History

Soniya Vyas 0c84f3ee2e Need to have stable tempest scenario manager This patch addresses following facts: 1. common manager methods among plugins should be defined in Tempest. 2. methods should be consistent with names and parameters. 3. Add docstring about method usage and parameter. Implements: blueprint tempest-scenario-manager-stable Signed-off by: Soniya Vyas<svyas@redhat.com> Change-Id: I191c8861c9ec29b78c9c8ad12ff2ddf3ffbf4db1		2020-09-03 15:49:53 +05:30
..
api	Wait until dependent resource is deleted	2020-08-31 18:21:46 +00:00
cmd	Improve unit tests for subunit_describe_calls	2020-08-18 17:25:21 -05:00
common	Remove checking of Accept-Range header	2020-07-08 08:55:18 +00:00
hacking	Update hacking for Python3	2020-04-04 10:33:23 +02:00
lib	Merge "Add response schema validation for volumes"	2020-08-14 05:32:22 +00:00
scenario	Need to have stable tempest scenario manager	2020-09-03 15:49:53 +05:30
services	Move the object client to tempest.lib	2017-10-17 00:14:20 +00:00
test_discover	Add logs for plugins data	2020-04-16 17:22:39 +00:00
tests	Merge "Add new tests for check-uuid tool"	2020-08-28 11:12:07 +00:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	services: Introduce a cinder v3 attachments client	2020-03-02 09:02:50 +00:00
config.py	Merge "Stop to use the __future__ module."	2020-07-28 13:01:46 +00:00
exceptions.py	Break wait_for_volume_resource_status when error_extending	2019-06-03 15:37:13 +08:00
manager.py	Need to have stable tempest scenario manager	2020-09-03 15:49:53 +05:30
test.py	Add workaround to handle the testtool skip exception in CLI test	2019-10-12 01:40:29 +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.