History

Masayuki Igawa fcacf96204 Introduce T106 rule for vi modelines We don't need to have the vi modelines in each source file anymore. We've already fixed them several times. https://review.openstack.org/#/c/66507/ https://review.openstack.org/#/c/68552/ https://review.openstack.org/#/c/69318/ https://review.openstack.org/#/c/70133/ However, newly some files still have it in its header. So we should check it automatically with our HACKING rule. This commit introduces T106 rule for that. Note: This code is copied from Nova's hacking rule. Change-Id: I347307a5145b2760c69085b6ca850d6a9137ffc6 Change-Id: I5c94ef041a39c2377ba6321ace8934f324287bcf Closes-Bug: #1229324		2014-02-20 11:42:35 +09:00
..
api	Merge "Adds list pool stat test case"	2014-02-20 01:30:49 +00:00
cli	Merge "unskip neutron_meter_label cli tests"	2014-02-18 09:43:24 +00:00
common	Merge "Fix request id log messages"	2014-02-20 01:30:30 +00:00
hacking	Introduce T106 rule for vi modelines	2014-02-20 11:42:35 +09:00
openstack	Sync Patch and PatchObject fixtures from oslo-incubator	2014-01-21 03:23:21 +00:00
scenario	Merge "Fixed misspellings in Tempest"	2014-02-19 07:59:41 +00:00
services	Merge "Adds list pool stat test case"	2014-02-20 01:30:49 +00:00
stress	Clean/leave OpenStack after a stress test	2014-02-05 16:53:06 +01:00
test_discover	Use unittest2.TestSuite with py26	2014-01-27 10:54:44 +01:00
tests	Ensure that bug number is actually a number for skip_because	2014-02-13 19:16:52 +00:00
thirdparty	Fixed misspellings in Tempest	2014-02-07 00:04:15 -08: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	Merge "auth.py is too verbose"	2014-02-12 15:39:45 +00:00
clients.py	Restore heat tests running with admin user, demo tenant	2014-02-19 10:03:57 +13:00
config.py	Merge "Make v2 and v3 identity apis configurable"	2014-02-18 08:30:44 +00:00
exceptions.py	Cleanup exceptions	2014-01-27 15:35:02 +09:00
manager.py	Remove last uses of config without global CONF object	2014-01-31 14:57:17 +00:00
test.py	Merge "Rename Openstack to OpenStack"	2014-02-18 12:47:32 +00: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.