17bad029a5
A recent change introduced a configuration option in the ./tests/test.yaml file (default location) which allows juju wait to be used rather than waiting on various workload messages. This, unfortunately, breaks mojo tests as they don't use a tests.yaml. This change refactors that code, and enables a 'use_juju_wait' to be passed into the relevant functions, and a new command line option (default true) to disable using juju wait.
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