History

Balazs Gibizer f294b0d8dc Test Network QoS minimum packet rate scenarios Depends-On: https://review.opendev.org/c/openstack/neutron/+/805391 Depens-On: https://review.opendev.org/c/openstack/nova/+/811396 blueprint: qos-minimum-guaranteed-packet-rate Change-Id: I4cb12a23f33d4feef6c800d23a0501d1aebb4f17		2021-11-29 15:17:25 +00:00
..
api	Merge "Remove race from wait_for_interface_detach waiter"	2021-11-15 14:14:11 +00:00
cmd	Merge "Update subunit_describe_calls about new ports"	2021-03-04 21:27:11 +00:00
common	Merge "Add floating IP waiter"	2021-11-23 18:03:52 +00:00
hacking	Fix hacking check for service client	2021-04-30 10:32:13 -05:00
lib	Test Network QoS minimum packet rate scenarios	2021-11-29 15:17:25 +00:00
scenario	Test Network QoS minimum packet rate scenarios	2021-11-29 15:17:25 +00:00
services	Remove usage of six	2021-02-18 10:43:57 +08:00
test_discover	Remove usage of six	2021-02-23 00:38:55 +00:00
tests	Merge "Add floating IP waiter"	2021-11-23 18:03:52 +00:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	Test Network QoS minimum packet rate scenarios	2021-11-29 15:17:25 +00:00
config.py	Test Network QoS minimum packet rate scenarios	2021-11-29 15:17:25 +00:00
exceptions.py	Break wait_for_volume_resource_status when error_extending	2019-06-03 15:37:13 +08:00
test.py	Remove usage of six	2021-04-15 09:25:19 +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.