openstack
/
tempest
Code Issues Proposed changes
OpenStack Testing (Tempest) of an existing cloud
1,630 Commits 1 Branch 45 Tags 244 MiB
Python 99.8%
Shell 0.2%
Go to file
Matthew Treinish 32d3570c18 Add unittest framework + tests for wrapper scripts 
This commit adds a framework for running unittests on tempest to
verify that tempest works as expect. The first tests added are to
verify the response codes of the test runner wrapper scripts we use
on jenkins jobs.

Change-Id: If8e91238054593999e7b5bc34da499bd0ac02311
 		2013-08-27 11:55:13 -04:00
bin Start making setup.py similar to other OpenStack Projects 2012-12-05 19:51:26 +01:00
doc/source Add unittest framework + tests for wrapper scripts 2013-08-27 11:55:13 -04:00
etc Merge "Add tenant isolation to the swift tests" 2013-08-22 05:21:30 +00:00
include Updating images tests 2011-10-31 15:23:19 -04:00
tempest Add unittest framework + tests for wrapper scripts 2013-08-27 11:55:13 -04:00
tools Fix skip tracker regex for multi-line skips 2013-08-19 10:14:54 -04:00
.gitignore Ignore .testrepository/ 2013-05-07 09:13:02 +12:00
.gitreview Update .gitreview with new project name. 2011-11-30 10:59:36 -08:00
.mailmap Update gitignore because of oslo setup.py 2013-01-09 10:54:17 -05:00
.testr.conf Add environmental variables to test.conf 2013-07-26 16:51:01 -04:00
HACKING.rst Fixing man page generation 2013-07-24 13:49:14 +02:00
LICENSE Add License to Tempest. 2012-04-12 16:04:36 +02:00
README.rst Fixing man page generation 2013-07-24 13:49:14 +02:00
openstack-common.conf Switching to oslo importutils in the stress tests 2013-07-31 13:18:47 +02:00
requirements.txt Update requirements from global requirements 2013-08-26 10:42:28 -04:00
run_tests.sh Add nose to run_tests and tox for python 2.6 2013-08-15 17:44:44 -04:00
setup.cfg Generate temepst API doc from source 2013-08-01 23:14:16 +00:00
setup.py Migrate to pbr from openstack.common.setup. 2013-05-01 14:04:27 -04:00
test-requirements.txt Update requirements from global requirements 2013-08-26 10:42:28 -04:00
tox.ini Add unittest framework + tests for wrapper scripts 2013-08-27 11:55:13 -04:00

README.rst

Tempest - The OpenStack Integration Test Suite

This is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, Scenarios, and other specific tests useful in validating an OpenStack deployment.

Quickstart

To run Tempest, you first need to create a configuration file that will tell Tempest where to find the various OpenStack services and other testing behavior switches.

The easiest way to create a configuration file is to copy the sample one in the etc/ directory :

$> cd $TEMPEST_ROOT_DIR
$> cp etc/tempest.conf.sample etc/tempest.conf

After that, open up the etc/tempest.conf file and edit the configuration variables to match valid data in your environment. This includes your Keystone endpoint, a valid user and credentials, and reference data to be used in testing.

Note

If you have a running devstack environment, tempest will be automatically configured and placed in /opt/stack/tempest. It will have a configuration file already set up to work with your devstack installation.

Tempest is not tied to any single test runner, but Nose been the most commonly used tool. After setting up your configuration file, you can execute the set of Tempest tests by using nosetests :

$> nosetests tempest

To run one single test :

$> nosetests -sv tempest.api.compute.servers.test_server_actions.py:
   ServerActionsTestJSON.test_rebuild_nonexistent_server

Configuration

Detailed configuration of tempest is beyond the scope of this document. The etc/tempest.conf.sample attempts to be a self documenting version of the configuration.

The most important pieces that are needed are the user ids, openstack endpoints, and basic flavors and images needed to run tests.

Common Issues

Tempest was originally designed to primarily run against a full OpenStack deployment. Due to that focus, some issues may occur when running Tempest against devstack.

Running Tempest, especially in parallel, against a devstack instance may cause requests to be rate limited, which will cause unexpected failures. Given the number of requests Tempest can make against a cluster, rate limiting should be disabled for all test accounts.

Additionally, devstack only provides a single image which Nova can use. For the moment, the best solution is to provide the same image uuid for both image_ref and image_ref_alt. Tempest will skip tests as needed if it detects that both images are the same.