openstack
/
tempest
Code Issues Proposed changes
OpenStack Testing (Tempest) of an existing cloud
976 Commits 1 Branch 45 Tags 240 MiB
Python 99.8%
Shell 0.2%
Go to file
Joe Gordon fc1808bc8e Add special serial smoke option 
We want smoketests to be parallel by default (for grenade etc), but that won't work
for neutron, so add a special case. Since we don't want to break
anything making this switch, it has to be done in 3 steps:

1) this patch
2) make neutron use smoke-serial
3) change smoke to be parallel

Note this is a backport to grizzly so the parallel options are not being
added, we are just maintaining serialized testing on the grizzly branch.

Change-Id: I03ded120c0b496026e39f14f6715624a91ac7558
 		2013-11-17 11:29:06 -08:00
bin Start making setup.py similar to other OpenStack Projects 2012-12-05 19:51:26 +01:00
cli Unskip cli-keystone catalog and help tests 2013-10-03 18:42:24 +02:00
etc Add ssh check to quantum smoke test. 2013-08-19 13:48:30 -07:00
include Updating images tests 2011-10-31 15:23:19 -04:00
stress Update stress tests to properly use tempest.config 2013-02-25 17:34:37 -05:00
tempest Fix precondition checks for test_network_basic_ops 2013-10-23 10:45:05 +02:00
tools Merge "Make skip_tracker bug keyword detection more robust." 2013-03-15 14:35:58 +00:00
.gitignore Update gitignore because of oslo setup.py 2013-01-09 10:54:17 -05: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 support for testrepository 2013-02-08 11:18:26 +10:30
HACKING.rst Update HACKING file. 2013-02-12 13:52:09 -05:00
LICENSE Add License to Tempest. 2012-04-12 16:04:36 +02:00
MANIFEST.in Add Manifest in order to include AUTHORS and ChangeLog 2013-09-19 10:50:38 +02:00
README.rst fix for Bug1078481 2012-11-20 00:09:43 +00:00
openstack-common.conf Use oslo.config-1.1.0b1 2013-03-06 10:14:01 -05:00
run_tests.sh Fix update option for run_tests.sh 2013-02-18 11:24:22 -05:00
setup.cfg Remove use of detailed-errors nose plugin 2013-01-31 10:55:54 +11:00
setup.py Set the proper version for grizzly. 2013-04-01 16:07:41 -04:00
tox.ini Add special serial smoke option 2013-11-17 11:29:06 -08:00

README.rst

:

Tempest - The OpenStack Integration Test Suite

This is a set of integration tests to be run against a live cluster.

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, look at the environment variables in your devstack/localrc file. The ADMIN_PASSWORD variable should match the api_key value in the tempest.conf [nova] configuration section. In addition, you will need to get the UUID identifier of the image that devstack uploaded and set the image_ref value in the [environment] section in the tempest.conf to that image UUID.

In addition, the <devstack-repo>/tools/configure_tempest.sh script can also be used to generate a tempest.conf based on your devstack's rc files. TEMPEST_DIR variable points to location /opt/stack/temptest. Update this variable if the location is different..

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.tests.compute.servers.test_server_actions.py:

ServerActionsTestJSON.test_rebuild_nonexistent_server

Configuration

At present, there are three sections to be configured: nova, environment, and image. The nova section includes information about your Keystone endpoint, as well as valid credentials for a user. It also contains logical timeouts for certain actions. The environment section contains reference data to be used when testing the Compute portion of OpenStack, as well as feature flags for tests that may or may not work based on your hypervisor or current environment. Lastly, the image section contains credentials and endpoints for the Glance image service.

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.