61472e147b
So far the Designate and Designate tempest plugin CI jobs definition
was different than most other OSP components. Some of the jobs were
defined in the Designate repository and other in the tempest plugin,
without any clear indication to the correct repository for the job type.
By adopting a modular approach similar to other OpenStack projects,
we'll reduce maintenance overhead and allow contributors to focus on
enhancing Designate rather than debugging CI structure issues.
Goals of this restructure process:
* Create a clear separation of job definitions between designate and
designate-tempest-plugin repositories
* Organize configurations into multiple files instead of single,
monolithic one
Closes-Bug: #2106143
Change-Id: I77a963f733ff6d04a7cead92655304de80205015
Signed-off-by: Omer <oschwart@redhat.com>
Team and repository tags
Tempest Integration of Designate
This directory contains Tempest tests to cover the designate project, as well as a plugin to automatically load these tests into tempest.
See the tempest plugin docs for information on using it: https://docs.openstack.org/tempest/latest/plugin.html#using-plugins
See the designate docs for information on writing new tests etc: https://docs.openstack.org/designate-tempest-plugin/latest/#writing-new-tests
Running the tests
From the tempest directory, setup the tempest virtual environment for the designate tempest plugin:
$ tox -e venv-tempest -- pip3 install -e <path to designate-tempest-plugin>For example, when using a typical devstack setup:
$ cd /opt/stack/tempest
$ tox -e venv-tempest -- pip3 install -e /opt/stack/designate-tempest-pluginTo run all tests from this plugin, install designate into your environment and from the tempest repo, run:
$ tox -e all -- designateTo run a single test case, run with the test case name, for example:
$ tox -e all -- designate_tempest_plugin.tests.api.v2.test_zones.ZonesTest.test_create_zonesTo run all tempest tests including this plugin, run:
$ tox -e all