Files

T

Ghanshyam Mann 2f4539d604 Stop testing volume v2 APIs

Cinder decided to remove the v2 APIs[1] in Xena cycle, so
in Tempest we need to modify the tempest-cinder-v2-api job
to run against stable wallaby which is last release where
volume v2 APIs are present.

Also ad deprecation warning at v2 service clients module level
import so that we can remove them once Tempest stop supporting
stable wallaby.

NOTE: we do not need to adjust any tests as we already moved all
the Tempest tests to volume v3 APIs.

Depends-On: https://review.opendev.org/c/openstack/devstack/+/791842

[1] https://wiki.openstack.org/wiki/CinderXenaPTGSummary#Removing_the_Block_Storage_API_v2

Change-Id: I98339f67239cf96d26aa4fa87df692139b36673d

2021-05-18 20:02:51 +00:00

api

Merge "Remove unicode from code"

2021-05-11 16:39:32 +00:00

cmd

Merge "Update subunit_describe_calls about new ports"

2021-03-04 21:27:11 +00:00

common

Add wait to check the import task status

2021-04-30 13:01:02 -05:00

hacking

Fix hacking check for service client

2021-04-30 10:32:13 -05:00

lib

Stop testing volume v2 APIs

2021-05-18 20:02:51 +00:00

scenario

Fix unstability in test_subnet_details

2021-03-29 08:31:15 +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 "Remove unicode from code"

2021-05-11 16:39:32 +00:00

__init__.py

…

clients.py

Add live migration with trunk test

2021-04-13 10:48:04 +00:00

config.py

Merge "Remove deprecated scenario img_dir option"

2021-03-22 18:32:16 +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

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.