openstack
/
charm-manila-generic
Code Issues Proposed changes
charm-manila-generic/src/tests
History
Alex Kavanagh c7aa6e1aeb Update to build using charmcraft 
Due to a build problem with the reactive plugin, this change falls back
on overriding the steps and doing a manual build, but it also ensures
the CI system builds the charm using charmcraft.  Changes:

- add a build-requirements.txt
- modify charmcraft.yaml
- modify osci.yaml
    -> indicate build with charmcraft
- modify tox.ini
    -> tox -e build does charmcraft build/rename
    -> tox -e build-reactive does the reactive build
- modify bundles to use the <charm>.charm artifact in tests.
  and fix deprecation warning re: prefix
- tox inception to enable tox -e func-test in the CI

Change-Id: I05dbf9cbfd3132b1970ca9cd9de111d6879f1582
 		2022-02-01 20:29:36 +00:00
..
bundles Update to build using charmcraft 2022-02-01 20:29:36 +00:00
README.md Migrate charm-manila-generic tests to Zaza 2020-06-17 11:26:44 +02:00
tests.yaml Migrate charm to charmhub latest/edge track 2022-01-28 16:27:19 +00:00

README.md

Overview

This directory provides Zaza tests to verify basic deployment functionality from the perspective of this charm, its requirements and its features, as exercised in a subset of the full OpenStack deployment test bundle topology.

For full details on functional testing of OpenStack charms please refer to the functional testing section of the OpenStack Charm Guide.