8cd6a06736
If the parent resource of a nested stack is locked due to an IN_PROGRESS update, cancel the nested stack update (which will result in the parent resource being marked FAILED and releasing the lock so that the new traversal can begin acting on it). This also cancels all descendants of the nested stack. This means that a concurrent update no longer gets blocked at a nested stack boundary until the previous update has finished. Change-Id: I5f14453ebab75d89672c6eea12de46d48a5147f3 Task: 17760 |
||
---|---|---|
.. | ||
common | ||
functional | ||
locale | ||
__init__.py | ||
cleanup_test_env.sh | ||
config-generator.conf | ||
post_test_hook.sh | ||
pre_test_hook.sh | ||
prepare_test_env.sh | ||
prepare_test_network.sh | ||
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:
export DEST=/opt/stack
# create test resources and write config
$DEST/heat/heat_integrationtests/prepare_test_env.sh
$DEST/heat/heat_integrationtests/prepare_test_network.sh
# run the heat integration tests
cd $DEST/heat
stestr --test-path=heat_integrationtests run
If the Heat Tempest Plugin is also installed, the tests from that will be run as well.
If custom configuration is required, add it in the file
heat_integrationtests/heat_integrationtests.conf
. A sample
configuration is available in
heat_integrationtests/heat_integrationtests.conf.sample