72752c4cdb
We need to specify doc requirements in doc/requirements.txt to avoid problems with the pip resolver [1] for the release team [2][3]. Removed specific doc requirements from test-requirements.txt. The problem here is that this repos haven't doc/requirements.txt file and by default in this case zuul will use the test-requirements.txt file to pull requirements [4]. This requirements file contains extra requirements like flake8 that collided with those allowed in our job environment and so the new pip resolver fails to install these requirements and the job exits in error. This project meet the conditions leading to the bug however it doesn't produce any doc or releasenotes, but uniformization can't hurt and help us in the future. /!\/!\/!\ Notice that I voluntarily added the doc directory even if no docs are generated here because zuul will try to pull this requirements from there first and the contained requirements are needed for reno but AFAIK the releasenotes dir is ignored by zuul. c.f [4] for further details. /!\/!\/!\ [1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html [3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36 Change-Id: I18fdf133b6c3ea9b60e784c0e1dfb7ce1217eda5 |
||
|---|---|---|
| cloudkitty_tempest_plugin | ||
| doc | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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