openstack/tempest
Code Issues Proposed changes
OpenStack Testing (Tempest) of an existing cloud
66 Commits 1 Branch 48 Tags 241 MiB
Python 99.8%
Shell 0.2%
ed8bef3a03
Go to file
Daryl Walleck ed8bef3a03 Changes the namespace from storm to tempest, as well as adding addition tests and improvements 
* Changed namespace from storm to tempest
* Added absolute limits service and server personality file tests
* Optimized run time for image metadata tests
* Added additional assertions for create server and rebuild server tests
* Removed any SSH verification until further decisions are made

Change-Id: I5bebd29be382c9404914c7314302670ae09627fc
2011-12-06 16:48:03 -06:00
etc Changes the namespace from storm to tempest, as well as adding addition tests and improvements 2011-12-06 16:48:03 -06:00
include Updating images tests 2011-10-31 15:23:19 -04:00
kong Fix numeric header values for kernel_id and ramdisk_id 2011-11-21 23:57:31 -06:00
tempest Changes the namespace from storm to tempest, as well as adding addition tests and improvements 2011-12-06 16:48:03 -06:00
tools Adding paramiko and unittest2 to pip-requires 2011-10-27 12:47:05 -04:00
.gitignore Fixes LP Bug#899383 - Cleanup config file search 2011-12-06 13:53:34 -05:00
.gitreview Update .gitreview with new project name. 2011-11-30 10:59:36 -08:00
HACKING Removed non-testing suggestions 2011-10-29 22:30:19 -05:00
README.rst Fixes LP Bug#899383 - Cleanup config file search 2011-12-06 13:53:34 -05:00
run_tests.sh Making run_test.sh python version and directory 2011-10-18 14:24:26 -05: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 behaviour 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/storm.conf.sample etc/storm.conf

After that, open up the etc/storm.conf file and edit the variables to fit your test environment.

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 storm.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 storm.conf to that image UUID.

After setting up your configuration file, you can execute the set of Tempest tests by using nosetests :

$> nosetests storm