OpenStack Testing (Tempest) of an existing cloud
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ghanshyam Mann da3bb61f1f Add index page for plugins documents 1 year ago
api compute: Add stable device rescue tests with BFV instances 1 year ago
cmd Merge "Remove the deprecated tempest-account-generator CLI" 1 year ago
common Merge "Fix noVNC failed TCs" 1 year ago
hacking Update hacking for Python3 2 years ago
lib compute: Add missing 2.73 response schema validation 1 year ago
scenario Explicitly handle baremetal ports when checking if they are active 1 year ago
services Move the object client to tempest.lib 4 years ago
test_discover Add logs for plugins data 1 year ago
tests Merge "Add --worker-file option in tempest" 1 year ago
README.rst Transfer respository to repository 3 years ago Changes the namespace from storm to tempest, as well as adding addition tests and improvements 10 years ago services: Introduce a cinder v3 attachments client 2 years ago Make image_ssh_password a secret so it does not show in console 1 year ago Break wait_for_volume_resource_status when error_extending 2 years ago Fix manager->get_auth_provider interface 5 years ago Add workaround to handle the testtool skip exception in CLI test 2 years ago Add reno to tempest 6 years ago


Tempest Field Guide Overview

Tempest is designed to be useful for a large number of different environments. This includes being useful for gating commits to OpenStack core projects, being used to validate OpenStack cloud implementations for both correctness, as well as a burn in tool for OpenStack clouds.

As such Tempest tests come in many flavors, each with their own rules and guidelines. Below is the overview of the Tempest repository structure to make this clear.

   api/ - API tests
   scenario/ - complex scenario tests
   tests/ - unit tests for Tempest internals

Each of these directories contains different types of tests. What belongs in each directory, the rules and examples for good tests, are documented in a README.rst file in the directory.


API tests are validation tests for the OpenStack API. They should not use the existing Python clients for OpenStack, but should instead use the Tempest implementations of clients. Having raw clients let us pass invalid JSON to the APIs and see the results, something we could not get with the native clients.

When it makes sense, API testing should be moved closer to the projects themselves, possibly as functional tests in their unit test frameworks.


Scenario tests are complex "through path" tests for OpenStack functionality. They are typically a series of steps where complicated state requiring multiple services is set up exercised, and torn down.

Scenario tests should not use the existing Python clients for OpenStack, but should instead use the Tempest implementations of clients.


Unit tests are the self checks for Tempest. They provide functional verification and regression checking for the internal components of Tempest. They should be used to just verify that the individual pieces of Tempest are working as expected.