openstack
/
charm-octavia-dashboard
Code Issues Proposed changes

Retarget Zaza to master now that split has landed 

This change is required as Zaza underwent a split of the openstack
tests from the Zaza project, so we had to track the working branch
until that change landed. As it has landed, it is now time to use
Zaza from master again

Change-Id: Id1ea4dbe7d7888cc20df19334b4ff33cf2df5090
This commit is contained in:
Chris MacNaughton 2019-05-22 12:25:44 +02:00
parent 01d1cb8b2c
commit 632801e8aa
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/test-requirements.txt
View File

@ -7,5 +7,5 @@ mock>=1.2
flake8>=2.2.4,<=2.4.1
stestr>=2.2.0
requests>=2.18.4
git+https://github.com/openstack-charmers/zaza.git@remove-namespaced-tests#egg=zaza
git+https://github.com/openstack-charmers/zaza.git#egg=zaza
git+https://github.com/openstack-charmers/zaza-openstack-tests.git#egg=zaza.openstack

4
src/tests/tests.yaml
View File

@ -15,6 +15,6 @@ target_deploy_status:
workload-status: blocked
workload-status-message: Awaiting
configure:
- zaza.openstack.charm_tests.noop.setup.basic_setup
- zaza.charm_tests.noop.setup.basic_setup
tests:
- zaza.openstack.charm_tests.noop.tests.NoopTest
- zaza.charm_tests.noop.tests.NoopTest