History

Steve Baker 1ad83200eb Add and use a StackResourceBuildErrorException wait_for_resource_status was raising a StackBuildErrorException with incorrect parameters, leading to an unhelpful error message. This will log the nova console to help diagnose Related-Bug: #1295396 Closes-Bug: #1295404 Change-Id: I979f9edcc0b57924fd3dd681b60165a3db311e6e		2014-04-01 10:38:31 +13:00
..
api	Add and use a StackResourceBuildErrorException	2014-04-01 10:38:31 +13:00
api_schema	Merge "Verify the response attributes of 'show_host_detail'"	2014-03-29 15:37:13 +00:00
cli	Merge "Skip volume snapshot tests if feature is not enabled"	2014-03-28 14:07:48 +00:00
common	Merge "Use HTTP_SUCCESS for checking success status code"	2014-03-31 07:40:56 +00:00
exceptions	Add and use a StackResourceBuildErrorException	2014-04-01 10:38:31 +13:00
hacking	Add missing client names to T102 hacking check	2014-03-15 21:41:00 -04:00
openstack	Update Oslo config sample generator	2014-03-17 15:04:12 +00:00
scenario	Skip volume snapshot tests if feature is not enabled	2014-03-25 17:46:06 +01:00
services	Add and use a StackResourceBuildErrorException	2014-04-01 10:38:31 +13:00
stress	Merge "stress/actions/ssh_floating.py n-net compatibility"	2014-03-15 08:35:52 +00:00
test_discover	Use unittest2.TestSuite with py26	2014-01-27 10:54:44 +01:00
tests	Merge "Add unit tests for NegativeRestClient class"	2014-03-28 07:33:44 +00:00
thirdparty	unskip test_integration_1	2014-03-20 11:27:53 +01: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	Renew token before expiry time	2014-03-24 14:00:15 +00:00
clients.py	Merge "Add agents tests for Nova v3 API"	2014-03-13 05:36:45 +00:00
config.py	Merge "Typo in config.py"	2014-03-29 00:43:04 +00:00
manager.py	Object storage tests to use default auth_provider	2014-03-13 10:35:18 +00:00
test.py	Deduplicate negative test calls	2014-03-26 13:56:09 +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.