| Matthew Treinish | a9aef87 | 2014-07-25 16:03:08 -0400 | [diff] [blame] | 1 | .. _third_party_field_guide: |
| 2 | |
| Masayuki Igawa | c268dd6 | 2013-09-18 00:51:05 +0900 | [diff] [blame] | 3 | Tempest Field Guide to Third Party API tests |
| 4 | ============================================ |
| Sean Dague | 09761f6 | 2013-05-13 15:20:40 -0400 | [diff] [blame] | 5 | |
| 6 | |
| 7 | What are these tests? |
| Attila Fazekas | 58d2330 | 2013-07-24 10:25:02 +0200 | [diff] [blame] | 8 | --------------------- |
| Sean Dague | 09761f6 | 2013-05-13 15:20:40 -0400 | [diff] [blame] | 9 | |
| 10 | Third party tests are tests for non native OpenStack APIs that are |
| 11 | part of OpenStack projects. If we ship an API, we're really required |
| 12 | to ensure that it's working. |
| 13 | |
| 14 | An example is that Nova Compute currently has EC2 API support in tree, |
| 15 | which should be tested as part of normal process. |
| 16 | |
| 17 | |
| 18 | Why are these tests in tempest? |
| Attila Fazekas | 58d2330 | 2013-07-24 10:25:02 +0200 | [diff] [blame] | 19 | ------------------------------- |
| Sean Dague | 09761f6 | 2013-05-13 15:20:40 -0400 | [diff] [blame] | 20 | |
| 21 | If we ship an API in an OpenStack component, there should be tests in |
| 22 | tempest to exercise it in some way. |
| 23 | |
| 24 | |
| 25 | Scope of these tests |
| Attila Fazekas | 58d2330 | 2013-07-24 10:25:02 +0200 | [diff] [blame] | 26 | -------------------- |
| Sean Dague | 09761f6 | 2013-05-13 15:20:40 -0400 | [diff] [blame] | 27 | |
| 28 | Third party API testing should be limited to the functional testing of |
| 29 | third party API compliance. Complex scenarios should be avoided, and |
| 30 | instead exercised with the OpenStack API, unless the third party API |
| 31 | can't be tested without those scenarios. |
| 32 | |
| 33 | Whenever possible third party API testing should use a client as close |
| 34 | to the third party API as possible. The point of these tests is API |
| 35 | validation. |