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