openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/api
History
Ken'ichi Ohmichi 0eb153c636 Remove wait_for_server_status from servers_client 
wait_for_server_status of compute client just calls the one of waiters
module and the method is a wrapper.
So the method seems redundant and it doesn't fit as service clients.

This patch removes wait_for_server_status from compute client and
replaces it with waiters' one.

Partially implements blueprint consistent-service-method-names

Change-Id: Ie821ea4ba0924b71caba80132e1c383fb5bb125d
 		2015-07-13 23:33:06 +00:00
..
baremetal Use the prefix-embedded rand_name method 2015-07-06 16:52:41 +12:00
compute Remove wait_for_server_status from servers_client 2015-07-13 23:33:06 +00:00
data_processing Use the prefix-embedded rand_name method 2015-07-06 16:52:41 +12:00
database Merge list_flavors_with_detail to list_flavors 2015-06-22 08:35:51 +00:00
identity Expanded assertion in test_create_token for keystone v2, v3 2015-07-07 12:02:30 +03:00
image Merge "Create test for private image" 2015-07-10 16:55:05 +00:00
messaging Use the prefix-embedded rand_name method 2015-07-06 16:52:41 +12:00
network Merge "Adding negative test cases for ports" 2015-07-08 10:27:22 +00:00
object_storage Use the prefix-embedded rand_name method 2015-07-06 16:52:41 +12:00
orchestration Merge "Use the prefix-embedded rand_name method" 2015-07-07 00:55:29 +00:00
telemetry Use the prefix-embedded rand_name method 2015-07-06 16:52:41 +12:00
volume Remove wait_for_server_status from servers_client 2015-07-13 23:33:06 +00:00
README.rst Add links to the field guide index 2014-07-25 16:03:08 -04:00
__init__.py Remove copyright from empty files 2014-01-14 03:02:04 +04:00
utils.py Prepare for enabling H302 (identity,volume,etc.) 2014-02-20 15:37:03 +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.