Go to file

Liam Young be8889e581 Move new methods out of test class

The new methods assertActionRanOK & assertRemoteRunOK are useful in
setup as well as tests so it makes sense to move them out of the
test class.

2020-04-01 10:18:30 +00:00

doc/source

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

tests

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

unit_tests

tidy up style things, add docstring

2020-03-25 08:44:41 +01:00

zaza

Move new methods out of test class

2020-04-01 10:18:30 +00:00

.gitignore

modify base zaza poackage into zaza.openstack package

2019-05-08 13:38:33 +02:00

.travis.yml

Fix lint

2019-06-27 11:33:52 +02:00

Add license, copyright and update package info

2018-08-08 16:11:04 -05:00

LICENSE

Add license, copyright and update package info

2018-08-08 16:11:04 -05:00

README.md

update readme

2019-05-09 10:53:24 +02:00

requirements.txt

Create parallel (async) series upgrade

2020-03-25 08:44:41 +01:00

setup.cfg

modify base zaza poackage into zaza.openstack package

2019-05-08 13:38:33 +02:00

setup.py

Pin OpenStack requirements to stable/train

2020-03-27 07:37:58 +01:00

tox.ini

Modified policyd tests to support openstack-dashboard

2019-11-20 17:23:26 +00:00

README.md

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.openstack.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