92101b18e2
In the legacy path we reparse a resource definition to refer to a different StackDefinition when copying a resource definition into the existing template (as the resource is updated) or into the backup stack's template. However, the resources 'condition' may reference conditionals that are not defined in the template it is being copied into (e.g. during a stack update that creates a new condition), and in this case the destination template will become unusable. Since the fact that we care about the resource definition at all indicates that the condition was enabled, just ignore the condition after reparsing. This is consistent with what we do for 'if' macros, which is to resolve the condition part during reparsing. Change-Id: I59a374435f6275badc8124efbd7b7db2e36e2de5 Story: #2003558 Task: 24847 |
||
|---|---|---|
| .. | ||
| common | ||
| functional | ||
| locale | ||
| .gitignore | ||
| README.rst | ||
| __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 runIf 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