History

Matt Riedemann 1395435e6a Get server fault if snapshot fails When we get a 404 from Glance because a server snapshot is not found while we're waiting for it to be ACTIVE, it means Nova deleted the failed snapshot from Glance because something failed in nova-compute during the snapshot operation. Rather than just dump a 404 in the test console output on this type of failure, this change gets the server which should have a fault recorded and uses that to raise a more useful error message for the test output. Change-Id: I8ee2e18925e7f4f09d10d857fb25f3d9b8e8bd42		2017-02-07 17:06:02 -05:00
..
api	Get server fault if snapshot fails	2017-02-07 17:06:02 -05:00
cmd	Replaces yaml.load() with yaml.safe_load()	2017-01-16 17:03:17 +07:00
common	Log server state changes when waiting for delete	2017-02-03 11:33:11 -05:00
hacking	Delete Savanna element in client list	2016-09-21 03:00:15 +00:00
lib	Merge "Fix date-time format checking in response schema"	2017-02-02 19:53:03 +00:00
scenario	Merge "Remove unused client from "_create_network" method"	2017-02-07 19:37:53 +00:00
services	Merge "Port object_storage tests to Py3."	2017-01-19 23:39:54 +00:00
test_discover	Use oslo.log library instead of system logging module	2017-01-16 05:56:54 +00:00
tests	Get server fault if snapshot fails	2017-02-07 17:06:02 -05:00
README.rst	Remove the Stress framework	2016-10-19 14:31:13 +02: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 default_params_with_timeout_values variable	2017-01-27 02:42:47 +00:00
config.py	Merge "Use oslo.log library instead of system logging module"	2017-01-16 18:22:03 +00:00
exceptions.py	Get server fault if snapshot fails	2017-02-07 17:06:02 -05: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 an unused variable in the BaseTestCase class	2017-01-04 19:17:35 +01: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

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.