30bc841b09
Adds a more comprehensive test for the cinder volume resources: - Creates a stack with a volume, and writes data to it - Deletes the stack with the volume deletion policy set to "snapshot" (which really means backup) the volume - Create a new stack with a volume created from the backup - Prove the data written in the first stack is still present Note this test also aims to provide coverage of volume attachment resources, e.g so we would catch any bugs like bug #1311533 in future. Authored-By: Steve Hardy <shardy@redhat.com> based on tempest change I04ae0cf942d12c4504b2df504a8c940575b90b69 Change-Id: I04ae0cf942d12c4504b2df504a8c940575b90b69 Related-Bug: #1311533 |
||
|---|---|---|
| .. | ||
| common | ||
| scenario | ||
| __init__.py | ||
| .gitignore | ||
| generate_sample.sh | ||
| heat_integrationtests.conf.sample | ||
| post_test_hook.sh | ||
| pre_test_hook.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:
# 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