tempest/tempest
Jordan Pittier 482e3ce6ab Remove the NegativeAutoTest Framework
Since it's not really used and a bit complex. It was only used
for negative compute flavor tests, and I think we can live easily
without these tests.

Change-Id: Iab676ae9bf95ee858c5e748c9579f7778e87bd77
2016-10-13 10:32:53 +02:00
..
api Remove the NegativeAutoTest Framework 2016-10-13 10:32:53 +02:00
cmd Merge "Use a common method for is a router interface" 2016-10-11 22:14:34 +00:00
common Use a common method for is a router interface 2016-10-07 20:42:24 +02:00
hacking Delete Savanna element in client list 2016-09-21 03:00:15 +00:00
lib Merge "Add test list namespace function" 2016-10-12 22:22:57 +00:00
scenario Merge "Fallback to creds provider for fixed IP network if no network_for_ssh" 2016-10-13 00:21:44 +00:00
services Merge "Fix docstrings in Tempest REST client for Ironic" 2016-10-12 23:14:39 +00:00
stress Add 'code-block' and revise tab 2016-09-30 23:35:31 +09:00
test_discover Only call register_service_clients if there are clients 2016-10-05 11:27:13 -04:00
tests Remove the NegativeAutoTest Framework 2016-10-13 10:32:53 +02:00
README.rst Deprecate meaningless TYPE 2016-08-26 09:59:02 +08:00
__init__.py Changes the namespace from storm to tempest, as well as adding addition tests and improvements 2011-12-06 16:48:03 -06:00
clients.py Remove Sahara tests from Tempest 2016-10-05 13:06:14 +02:00
config.py Merge "Remove Sahara tests from Tempest" 2016-10-11 18:59:52 +00:00
exceptions.py Migrate backups clients to tempest.lib 2016-10-02 09:37:46 +00:00
manager.py Merge "Revert "Move dscv and ca_certs to config section service_clients"" 2016-08-20 22:48:10 +00:00
test.py Remove the NegativeAutoTest Framework 2016-10-13 10:32:53 +02: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 proposed Havana restructuring for Tempest to make this clear.

tempest/
   api/ - API tests
   scenario/ - complex scenario tests
   stress/ - stress 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.

stress_field_guide

Stress tests are designed to stress an OpenStack environment by running a high workload against it and seeing what breaks. The stress test framework runs several test jobs in parallel and can run any existing test in Tempest as a stress job.

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.