History

Lee Yarwood 5423c53095 scenario: Use wait_for_volume_attachment_remove_from_server in nova_volume_detach Detaching a volume from an instance in Nova is an asynchronous operation. While the request can be accepted the underlying act of detaching the device from the instance, disconnecting the volume from the host, updating cinder and deleting records in Nova can take some considerable time. As such when detaching a volume callers should continue to poll the os-volume_attachments Nova API to determine when the underlying volume attachment, also known as a Block Device Mapping or BDM, is removed. Bug #1908399 outlines an issue where the scenario helper method nova_volume_detach was being called multiple times during tests and cleanup while only waiting for the volume status to change to available. This allowed for a race to occur where additional requests could be made to detach the volume while the volume attachment still remained in Nova resulting in a 400 error being returned by n-api. This change addresses this by switching between the volume resource status and the volume attachment removal waiters. Closes-Bug: #1908399 Change-Id: Ib6ae2c30be65eb444976b0330fd23d9457146284		2020-12-21 16:05:35 +00:00
..
api	Merge "compute: Skip AttachVolumeShelveTestJSON when cross_az_attach unavailable"	2020-12-08 16:59:33 +00:00
cmd	Merge "Remove six.PY3/six.PY2"	2020-11-27 01:52:40 +00:00
common	Remove race due to 1907084	2020-12-07 16:41:16 +01:00
hacking	Update hacking for Python3	2020-04-04 10:33:23 +02:00
lib	Merge "Add tag in compute interfaces schema for microversion 2.70"	2020-12-04 07:19:23 +00:00
scenario	scenario: Use wait_for_volume_attachment_remove_from_server in nova_volume_detach	2020-12-21 16:05:35 +00:00
services	Move the object client to tempest.lib	2017-10-17 00:14:20 +00:00
test_discover	Use os.path.join as possible	2020-09-06 09:49:40 +00:00
tests	Remove race due to 1907084	2020-12-07 16:41:16 +01:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
__init__.py	…
clients.py	Add placement API methods for testing routed provider nets	2020-09-28 06:45:37 +00:00
config.py	Merge "Allow additional port_vnic_type"	2020-12-07 15:07:13 +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.