History

Matthew Treinish a9aef878f0 Add links to the field guide index This commit takes the subsection summary in the field guid index and adds internal links to the field guide page. Previously when viewing the field guide docs it wasn't clear how to navigate between all the different test class pages, this is remedied by adding a link. Change-Id: Ica93a92c57e5d5d805a8b25d7c7e17509695152b		2014-07-25 16:03:08 -04:00
..
boto	Exclude volume tags while listing instance tags	2014-07-07 18:03:49 +05:30
README.rst	Add links to the field guide index	2014-07-25 16:03:08 -04:00
__init__.py	move boto tests to thirdparty directory - part 1	2013-05-17 08:52:25 -04:00

README.rst

Tempest Field Guide to Third Party API tests

What are these tests?

Third party tests are tests for non native OpenStack APIs that are part of OpenStack projects. If we ship an API, we're really required to ensure that it's working.

An example is that Nova Compute currently has EC2 API support in tree, which should be tested as part of normal process.

Why are these tests in tempest?

If we ship an API in an OpenStack component, there should be tests in tempest to exercise it in some way.

Scope of these tests

Third party API testing should be limited to the functional testing of third party API compliance. Complex scenarios should be avoided, and instead exercised with the OpenStack API, unless the third party API can't be tested without those scenarios.

Whenever possible third party API testing should use a client as close to the third party API as possible. The point of these tests is API validation.