openstack
/
tempest
Code Issues Proposed changes
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
34.2.0
34.1.0
34.0.0
wallaby-last
33.0.0
32.0.0
31.1.0
31.0.0
victoria-last
ussuri-last
30.1.0
30.0.0
29.2.0
29.1.0
29.0.0
28.1.0
28.0.0
train-last
27.0.0
26.1.0
stein-last
26.0.0
25.0.1
25.0.0
24.0.0
23.0.0
queens-em
22.1.0
22.0.0
21.0.0
ocata-em
20.0.0
19.0.0
18.0.0
17.2.0
17.1.0
17.0.0
16.1.0
16.0.0
15.0.0
14.0.0
13.0.0
12.2.0
12.1.0
12.0.0
11.0.0
10.0.0
9
8
7
6
5
4
3
2
havana-eol
1
grizzly-eol
folsom-eol
essex-eol
diablo-eol
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '2e7ae7c6e5'
${ noResults }
tempest/tempest
History
Jordan Pittier 2e7ae7c6e5 Remove the Stress framework 
It's not used anymore. There was general consensus in Feb 2016
to deprecate it (see [1]) and remove it in Newton.

[1]  [qa] deprecating Tempest stress framework

Change-Id: Ib229985ea2a1fee495c9492c9ce1781e6bac1dc6
 		7 years ago
..
api Remove the Stress framework 7 years ago
cmd Remove the Stress framework 7 years ago
common Move InvalidConfiguration exception to tempest.lib 7 years ago
hacking Delete Savanna element in client list 7 years ago
lib Merge "Move InvalidConfiguration exception to tempest.lib" 7 years ago
scenario Remove the Stress framework 7 years ago
services Move volume service clients under tempest.lib 7 years ago
test_discover Only call register_service_clients if there are clients 7 years ago
tests Remove the Stress framework 7 years ago
README.rst Remove the Stress framework 7 years ago
__init__.py
…
clients.py Move InvalidConfiguration exception to tempest.lib 7 years ago
config.py Remove the Stress framework 7 years ago
exceptions.py Move InvalidConfiguration exception to tempest.lib 7 years ago
manager.py Merge "Revert "Move dscv and ca_certs to config section service_clients"" 7 years ago
test.py Remove the Stress framework 7 years ago
version.py Add reno to tempest 7 years ago

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 proposed Havana restructuring for Tempest to make this clear.

tempest/
   api/ - API tests
   scenario/ - complex scenario tests

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.