openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/api
History
Bartosz Górski ab33b7e502 Adds tests for Heat 
Tests and client methods for:
- template-show
- template-validate
- template-url-validate
- stack-list
- stack-show
- resource-list
- resource-show
- resource-metadata
- event-list
- event-show

Testing Neutron resources:
- network
- subnet
- router_interface

Testing server property:
- subnet_id

Change-Id: I47bb0dd653da51c9ff1d2ffe0b02c102cc0098d5
 		2013-08-26 09:49:53 -07:00
..
compute Merge "use assertIsNotNone instead of assertNotEqual(*, None)" 2013-08-23 23:00:50 +00:00
identity Merge "Protected matcher import" 2013-08-24 16:05:55 +00:00
image setUpClass/tearDownClass full chain 2013-08-14 16:26:44 +02:00
network Adding network api xml support 2013-08-20 20:15:16 +05:30
object_storage Merge "Add more tests for Swift Account Quota" 2013-08-23 21:58:03 +00:00
orchestration Adds tests for Heat 2013-08-26 09:49:53 -07:00
volume Merge "setUpClass/tearDownClass full chain" 2013-08-15 13:25:30 +00:00
README.rst Fix typos in tempest/api/README.rst 2013-08-15 13:59:42 +08:00
__init__.py rename tests -> api 2013-05-20 17:20:54 -04:00
utils.py Use nose skip exception conditionally 2013-07-24 15:28:53 +10:00

README.rst

Tempest 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.