| Attila Fazekas | 58d2330 | 2013-07-24 10:25:02 +0200 | [diff] [blame] | 1 | ============================ |
| Sean Dague | 7679b48 | 2013-05-24 08:49:44 -0400 | [diff] [blame] | 2 | Tempest Field Guide Overview |
| Attila Fazekas | 58d2330 | 2013-07-24 10:25:02 +0200 | [diff] [blame] | 3 | ============================ |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 4 | |
| 5 | Tempest is designed to be useful for a large number of different |
| 6 | environments. This includes being useful for gating commits to |
| 7 | OpenStack core projects, being used to validate OpenStack cloud |
| 8 | implementations for both correctness, as well as a burn in tool for |
| 9 | OpenStack clouds. |
| 10 | |
| 11 | As such Tempest tests come in many flavors, each with their own rules |
| 12 | and guidelines. Below is the proposed Havana restructuring for Tempest |
| 13 | to make this clear. |
| 14 | |
| Xiao Hanyu | a4036d1 | 2013-06-19 14:12:23 +0800 | [diff] [blame] | 15 | | tempest/ |
| 16 | | api/ - API tests |
| Xiao Hanyu | a4036d1 | 2013-06-19 14:12:23 +0800 | [diff] [blame] | 17 | | scenario/ - complex scenario tests |
| 18 | | stress/ - stress tests |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 19 | |
| 20 | Each of these directories contains different types of tests. What |
| 21 | belongs in each directory, the rules and examples for good tests, are |
| 22 | documented in a README.rst file in the directory. |
| 23 | |
| Matthew Treinish | a9aef87 | 2014-07-25 16:03:08 -0400 | [diff] [blame] | 24 | :ref:`api_field_guide` |
| 25 | ---------------------- |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 26 | |
| 27 | API tests are validation tests for the OpenStack API. They should not |
| 28 | use the existing python clients for OpenStack, but should instead use |
| 29 | the tempest implementations of clients. This allows us to test both |
| 30 | XML and JSON. Having raw clients also lets us pass invalid JSON and |
| 31 | XML to the APIs and see the results, something we could not get with |
| 32 | the native clients. |
| 33 | |
| 34 | When it makes sense, API testing should be moved closer to the |
| 35 | projects themselves, possibly as functional tests in their unit test |
| 36 | frameworks. |
| 37 | |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 38 | |
| Matthew Treinish | a9aef87 | 2014-07-25 16:03:08 -0400 | [diff] [blame] | 39 | :ref:`scenario_field_guide` |
| 40 | --------------------------- |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 41 | |
| 42 | Scenario tests are complex "through path" tests for OpenStack |
| 43 | functionality. They are typically a series of steps where complicated |
| 44 | state requiring multiple services is set up exercised, and torn down. |
| 45 | |
| ghanshyam | 50f1947 | 2014-11-26 17:04:37 +0900 | [diff] [blame] | 46 | Scenario tests should not use the existing python clients for OpenStack, |
| 47 | but should instead use the tempest implementations of clients. |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 48 | |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 49 | |
| Matthew Treinish | a9aef87 | 2014-07-25 16:03:08 -0400 | [diff] [blame] | 50 | :ref:`stress_field_guide` |
| 51 | ------------------------- |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 52 | |
| Marc Koderer | a58e851 | 2014-07-17 10:40:23 +0200 | [diff] [blame] | 53 | Stress tests are designed to stress an OpenStack environment by running a high |
| 54 | workload against it and seeing what breaks. The stress test framework runs |
| 55 | several test jobs in parallel and can run any existing test in Tempest as a |
| 56 | stress job. |
| Sean Dague | 31a57ad | 2013-05-07 15:24:05 -0400 | [diff] [blame] | 57 | |
| Matthew Treinish | 817a808 | 2014-07-25 16:07:20 -0400 | [diff] [blame] | 58 | :ref:`unit_tests_field_guide` |
| 59 | ----------------------------- |
| 60 | |
| 61 | Unit tests are the self checks for Tempest. They provide functional |
| 62 | verification and regression checking for the internal components of tempest. |
| 63 | They should be used to just verify that the individual pieces of tempest are |
| 64 | working as expected. |