openstack
/
tempest
Code Issues Proposed changes
tempest/tempest/thirdparty
History
Andrey Pavlov 5fbfdcdd35 remove skip attributes for fixed bug 
1. remove skip attributes for test_run_terminate_instance

2. add forgotten changes for commit
   55c597db0f
   (Fix InvalidInstanceID.NotFound handling)

Change-Id: I616a90f98e3874a09274d961345476d47d266db0
 		2014-05-27 12:54:04 +04:00
..
boto remove skip attributes for fixed bug 2014-05-27 12:54:04 +04:00
README.rst Add 'Field' to the title of the Field Guides 2013-09-18 13:29:53 +09: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.