History

Matthew Treinish 56c1a55d26 Add bug skip for test_container_synchronization() This commit adds a skip to test_container_synchronization(). This test currently only gets run during the periodic -all job because of it's slow tag. It is currently failing 100% of the time and has been in this state for quite some time. So let's skip it until the underlying bug is fixed. Related-Bug: #1317133 Change-Id: Iff71b74a377cf80be21516c546031e784a61f836		2014-06-09 15:31:59 +00:00
..
api	Add bug skip for test_container_synchronization()	2014-06-09 15:31:59 +00:00
api_schema	Merge "Verify server list_addresses V2/V3 APIs attributes"	2014-06-02 06:25:05 +00:00
cli	add test for command bash-completion	2014-05-15 08:58:46 +00:00
cmd	javelin 2	2014-05-29 12:15:23 -04:00
common	Merge "Switch back to nc in test_load_balancer_basic"	2014-06-03 15:31:25 +00:00
hacking	Add noqa support to no_setupclass_for_unit_tests	2014-05-02 19:14:28 -04:00
openstack	Update Oslo config sample generator	2014-03-17 15:04:12 +00:00
scenario	Revert "Fail fast during advanced networking test"	2014-06-05 16:18:42 +00:00
services	Merge "adds tests for CINDER encryption volume-type APIs"	2014-06-04 12:23:06 +00:00
stress	Enforces the use of Credentials (part2)	2014-05-06 14:38:55 +01:00
test_discover	Use unittest2.TestSuite with py26	2014-01-27 10:54:44 +01:00
tests	Merge "Start using oslotest for tempest unit tests"	2014-05-30 14:31:09 +00:00
thirdparty	remove skip attributes for fixed bug	2014-05-27 12:54:04 +04:00
README.rst	Remove Whitebox tests	2013-09-12 15:40:15 +00: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
auth.py	Use auth data to fill credentials	2014-04-30 13:36:14 +01:00
clients.py	Merge "Add tests for availability-zone-list CINDER V1 API"	2014-05-29 14:08:17 +00:00
config.py	provide ability to tweak oslo log defaults	2014-06-07 07:51:16 -04:00
exceptions.py	Merge "Add a lacking message format letter 's'"	2014-05-06 09:56:02 +00:00
manager.py	Enforces the use of Credentials (part2)	2014-05-06 14:38:55 +01:00
test.py	Enforces the use of Credentials (part2)	2014-05-06 14:38:55 +01: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
   cli/ - CLI tests
   scenario/ - complex scenario tests
   stress/ - stress tests
   thirdparty/ - 3rd party api 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

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. This allows us to test both XML and JSON. Having raw clients also lets us pass invalid JSON and XML 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.

cli

CLI tests use the openstack CLI to interact with the OpenStack cloud. CLI testing in unit tests is somewhat difficult because unlike server testing, there is no access to server code to instantiate. Tempest seems like a logical place for this, as it prereqs having a running OpenStack cloud.

scenario

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 can and should use the OpenStack python clients.

stress

Stress tests are designed to stress an OpenStack environment by running a high workload against it and seeing what breaks. Tools may be provided to help detect breaks (stack traces in the logs).

TODO: old stress tests deleted, new_stress that david is working on moves into here.

thirdparty

Many openstack components include 3rdparty API support. It is completely legitimate for Tempest to include tests of 3rdparty APIs, but those should be kept separate from the normal OpenStack validation.