History

Angus Salkeld 3c9bdbeae6 Move nested stack delete test to functional This tries to prove that if you manually delete a nested stack, the parent stack is still deletable. part of blueprint decouple-nested Change-Id: I1d0bf7b5d982dc1f312fbe70cbb09a2e624e3371		2015-02-17 21:14:38 +10:00
..
common	Merge "Move assign_keypair method in base class"	2015-02-13 13:57:40 +00:00
functional	Move nested stack delete test to functional	2015-02-17 21:14:38 +10:00
scenario	Move assign_keypair method in base class	2015-02-13 06:27:14 -05:00
.gitignore	Support classes for heat integration tests	2014-09-24 09:02:20 +12:00
README.rst	Fix formatting in integration tests README	2014-12-08 11:47:18 +02:00
__init__.py	Support classes for heat integration tests	2014-09-24 09:02:20 +12:00
config-generator.conf	Get tox to generate config for heat_integrationtests	2015-02-04 00:01:26 +05:30
heat_integrationtests.conf.sample	Merge "Skip Stack Adopt/Abandon integration tests when Stack Adopt is disabled"	2015-02-13 08:40:18 +00:00
post_test_hook.sh	Configure flavor and image from env	2014-10-08 10:16:30 +13:00
pre_test_hook.sh	Move template resource tests to functional	2015-01-12 23:07:05 +10:00

README.rst

Heat integration tests

These tests can be run against any heat-enabled OpenStack cloud, however defaults match running against a recent DevStack.

To run the tests against DevStack, do the following:

# source DevStack credentials

source /opt/stack/devstack/accrc/demo/demo

# run the heat integration tests with those credentials

cd /opt/stack/heat

tox -eintegration

If custom configuration is required, copy the following file:

heat_integrationtests/heat_integrationtests.conf.sample

to:

heat_integrationtests/heat_integrationtests.conf

and make any required configuration changes before running:

tox -eintegration