openstack/tempest

History

Dan Smith 2c192f46db Chunked GET request support In one test, we are downloading the entire image (into memory) and re-uploading it. That works when the image is 16MiB but not when it is 1GiB. This adds support to the internal http client for chunked downloads (similar to upload), makes the image client able to take that flag, and finally makes the offending test do a chunked upload/ download streaming operation. Note this un-skips the test, effectively reverting `a6b7e334c` because the test should no longer consume large amounts of memory. Related-Bug: #2002951 Change-Id: I31e537538a1862e71091aa470da3b8e9c799bf15		2023-01-25 06:38:19 -08:00
..
api	Chunked GET request support	2023-01-25 06:38:19 -08:00
cmd	Remove compute api_extensions config option	2022-05-05 18:15:29 -05:00
common	Add support for dhcpcd in the renew_lease method	2023-01-23 11:39:39 +00:00
hacking	Use LOG.warning instead of deprecated LOG.warn	2022-01-19 13:38:21 +09:00
lib	Chunked GET request support	2023-01-25 06:38:19 -08:00
scenario	Introduce @serial test execution decorator	2023-01-18 02:45:43 +00:00
serial_tests	Introduce @serial test execution decorator	2023-01-18 02:45:43 +00:00
test_discover	Introduce @serial test execution decorator	2023-01-18 02:45:43 +00:00
tests	Chunked GET request support	2023-01-25 06:38:19 -08:00
__init__.py
clients.py	Add test for compute server external event API	2022-11-21 20:30:35 +00:00
config.py	Add support for dhcpcd in the renew_lease method	2023-01-23 11:39:39 +00:00
exceptions.py	Break wait_for_volume_resource_status when error_extending	2019-06-03 15:37:13 +08:00
README.rst	Transfer respository to repository	2018-12-09 19:59:12 +08:00
test.py	Introduce @serial test execution decorator	2023-01-18 02:45:43 +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.