Alex Kavanagh 7c8a190e7a Ensure unittests use zaza non-threaded
zaza normally runs libjuju async functions in a background thread
to enable zaza to be blocking, but keep the libjuju async functions
'ticking over' between blocking calls.

This can break unit tests as starting the zaza background thread will
hang unless it is cleaned up.  A simple solution is just to use zaza in
non-threaded mode in the unit tests, and zaza provides a mechanism for
this via zaza.RUN_LIBJUJU_IN_THREAD = False.
2022-07-08 11:03:04 +01:00
2022-04-22 14:34:22 +02:00
2020-06-11 15:53:51 +00:00
2021-07-29 09:56:23 +01:00
2020-04-02 15:44:17 +02:00
2022-07-05 12:06:02 +01:00
2021-07-28 16:53:01 +02:00

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
Description
No description provided
Readme Apache-2.0 3.8 MiB
Languages
Python 99.6%
Jinja 0.4%