History

Jenkins e5021be496 Merge "unskip test_list_non_public_flavor"		2014-02-19 08:09:09 +00:00
..
baremetal	Convert ironic, swift, and heat api tests to use global CONF object	2014-01-30 19:56:51 +00:00
compute	Merge "unskip test_list_non_public_flavor"	2014-02-19 08:09:09 +00:00
data_processing	Merge "Add missing isolated_cred cleanup to savanna tests"	2014-02-13 03:40:02 +00:00
identity	Merge "Make v2 and v3 identity apis configurable"	2014-02-18 08:30:44 +00:00
image	port nova v2 images related tests into nova v3 part2	2014-02-17 13:38:18 +08:00
network	Merge "Refactor create_ and update_ methods for VIPs and health_monitors"	2014-02-18 11:02:11 +00:00
object_storage	Multiversion authentication part1	2014-02-05 11:34:53 +00:00
orchestration	Convert ironic, swift, and heat api tests to use global CONF object	2014-01-30 19:56:51 +00:00
telemetry	Add CRUD tests for telemetry alarming	2014-02-12 20:01:18 +04:00
volume	Merge "Add some cases about volume-create and volume-rename"	2014-02-18 08:09:55 +00:00
README.rst	Add 'Field' to the title of the Field Guides	2013-09-18 13:29:53 +09:00
__init__.py	Remove copyright from empty files	2014-01-14 03:02:04 +04:00
utils.py	Remove vim headers	2014-01-20 11:22:45 +09:00

README.rst

Tempest Field Guide to API tests

What are these tests?

One of Tempest's prime function is to ensure that your OpenStack cloud works with the OpenStack API as documented. The current largest portion of Tempest code is devoted to test cases that do exactly this.

It's also important to test not only the expected positive path on APIs, but also to provide them with invalid data to ensure they fail in expected and documented ways. Over the course of the OpenStack project Tempest has discovered many fundamental bugs by doing just this.

In order for some APIs to return meaningful results, there must be enough data in the system. This means these tests might start by spinning up a server, image, etc, then operating on it.

Why are these tests in tempest?

This is one of the core missions for the Tempest project, and where it started. Many people use this bit of function in Tempest to ensure their clouds haven't broken the OpenStack API.

It could be argued that some of the negative testing could be done back in the projects themselves, and we might evolve there over time, but currently in the OpenStack gate this is a fundamentally important place to keep things.

Scope of these tests

API tests should always use the Tempest implementation of the OpenStack API, as we want to ensure that bugs aren't hidden by the official clients.

They should test specific API calls, and can build up complex state if it's needed for the API call to be meaningful.

They should send not only good data, but bad data at the API and look for error codes.

They should all be able to be run on their own, not depending on the state created by a previous test.