Frode Nordahl
9203865408
There are two problems with doing so as part of individual functional tests: 1) If the application already have the value set the test will time out waiting for a change that will never be made. 2) python-libjuju ``set_config`` call requires values to be ``str`` regardless of their actual type. Pairing this fact with the requirement to use the actual type when comparing values before attempting to set them makes this very confusing and error prone. juju/python-libjuju#388 openstack-charmers/zaza#348 Use the ``config_change`` helper instead.
Zaza OpenStack Tests
This is a test library designed to be shared between the OpenStack Charms to improve code-reuse among the various components.
Usage
This example is taken from the pacemaker-remote charm's tests.yaml:
charm_name: pacemaker-remote
tests:
- zaza.openstack.charm_tests.pacemaker_remote.tests.PacemakerRemoteTest
configure:
- zaza.charm_tests.noop.setup.basic_setup
gate_bundles:
- basic
smoke_bundles:
- basic
test-requirements.txt:
git+https://github.com/openstack-charmers/zaza.git#egg=zaza
git+https://github.com/openstack-charmers/zaza-openstack-tests.git#egg=zaza.openstack