History

Swapnil Chhanikar a89eea8559 Change default region for placement to empty string As per tempest design, if tempest conf is not having any region for a service then identity region should be used. In case of placement the default value is "RegionOne" which is considered as placement region if region missing in tempest conf. In order to have identity region to be used as default we need to change to empty string for placement service. Empty string can be seen being used in other services like volume, image etc. Please check the below link for the logic of default region https://github.com/openstack/tempest/blob/master/tempest/config.py#L1435 Change-Id: I2a1045cd0f9eb830493b2b4287ccee46223f3c59		2020-02-03 09:12:35 +00:00
..
api	Merge "Create default network for more compute tests"	2020-01-28 17:57:41 +00:00
cmd	Tempest cleanup: improve iterating over projects	2019-12-20 08:59:54 +00:00
common	Fix test_stamp_pattern to remove dependency of user supplied volume name	2020-01-24 19:19:45 -05:00
hacking	Merge "Bump hacking to 1.1.0"	2018-08-21 12:46:22 +00:00
lib	Merge "Add ConsistencyGroup Exceptions in tempest"	2020-01-28 17:43:41 +00:00
scenario	Merge "Fix test_stamp_pattern to remove dependency of user supplied volume name"	2020-01-28 17:39:14 +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	Merge "Fix test_stamp_pattern to remove dependency of user supplied volume name"	2020-01-28 17:39:14 +00:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	Add segments client	2019-07-25 10:56:06 +02:00
config.py	Change default region for placement to empty string	2020-02-03 09:12:35 +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 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.