6cf8dc6e56
If we use unicode as resource name or parameter, we are likely to encounter unicode problems. This patch aims to fix unicode problems, and there are several things to be clear: 1. For the class wrap with six.python_2_unicode_compatible, in python2 their original __str__ function will map to __unicode__, and new __str__ function comes from __unicode__.encode. So we should always return unicode in __str__() if wrap with python_2_unicode_compatible. 2. python_2_unicode_compatible will not handle __repr__, __repr__ should return str in all versions of python. Co-Authored-By: Ethan Lynn <xjunlin@cn.ibm.com> Closes-Bug: #1524194 Change-Id: Ib4af43d153e0edf9d66308bf8e7b93a3be501d2e |
||
---|---|---|
.. | ||
common | ||
functional | ||
scenario | ||
__init__.py | ||
.gitignore | ||
config-generator.conf | ||
heat_integrationtests.conf.sample | ||
post_test_hook.sh | ||
pre_test_hook.sh | ||
prepare_test_env.sh | ||
prepare_test_network.sh | ||
README.rst | ||
requirements.txt |
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/openrc
# 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