3713d78d5d
stable/2023.1 is planned to be in unmaintained state[1] and with python 3.8 drop from Tempest[2], we have to pin the Tempest for stable/2023.1 testing[3]. This means Tempest and its plugin master does not need to support stable/2023.1. With that we can remove the stable/2023.1 jobs from tempest plugin master jobs. [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/UDQAC7SR5JAQJE5WBAG54A2MTBVBTJ44/ [2] https://review.opendev.org/c/openstack/tempest/+/933398 [3] https://review.opendev.org/c/openstack/devstack/+/933704 Change-Id: If3eb05555bace8c0dd17412d99b9f5fb1303cb6b
Tempest integration of CloudKitty
This project defines a tempest plugin containing tests used to verify the functionality of a cloudkitty installation. The plugin will automatically load these tests into tempest.
Dependencies
This plugin tests the CloudKitty API. This supposes that the 'rating' role exists in your OpenStack installation.
Developers
For more information on cloudkitty, refer to: https://docs.openstack.org/cloudkitty/latest/
For more information on tempest plugins, refer to: https://docs.openstack.org/tempest/latest/#using-plugins
Bugs
Please report bugs to: https://storyboard.openstack.org/#!/project/890
Installing
Clone this repository and call from the repo:
$ pip install -e .Running the tests
To run all the tests from this plugin, call from the tempest repo:
$ cd <Tempest Directory>
$ tox -e all -- cloudkitty_tempest_pluginTo run a single test case, call with full path, for example:
$ cd <Tempest Directory>
$ tox -e all -- cloudkitty_tempest_plugin.tests.api.test_cloudkitty_api.CloudkittyAdminAPITest.test_get_collector_mappingsTo retrieve a list of all tempest tests, run:
$ cd <Tempest Directory>
$ testr list-tests