Functional tests are meant to validate the openstack optimize cli
functionality. The code was kept in watcher-tempest-plugin repo.
Tempest plugin repo was meant to store tempest related api and
scenario tests, not functional tests. This patch moves the code
from watcher-tempest-plugin to watcherclient repo.
It also adds:
- tox target for running functional tests
- New zuul job based on devstack-tox-functional to run functional
tests.
Note: Now functional tests are running via tox and OS_* variable.
That's why It also drops tempest credentials factory to get creds from
tempest.conf.
Related-bug: #2100741
Change-Id: Ibf25c9cd6b8cd6b228f759d7393af5fe6a357d7f
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
As per the current release tested runtime, we test
python version from 3.8 to 3.11 so updating the
same in python classifier in setup.cfg
Change-Id: I3a938c4d27f987f4fa1a60d41baf9da74b32a78f
The lower constraints job was already removed[1] and the file content
is no longer tested.
[1] 52a3fd062d0ab754130152e9c73aac86ace02673
Change-Id: Ife61e9de574bc0fd78bd733a33e41ac6cb48d12d
This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I8343a54a94d64741325c0cbdd89e01e939bf73ac
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed that
python-watcherclient could not be built reproducibly.
This is because the documentation generates automatic documentation for
the "main()" entrypoint method's arguments, one of which is "sys.argv".
During document generation this results in documentation examples like:
def main(argv=['-b', 'html', 'doc/source',
'«ABSOLUTE_BUILD_DIR»/debian/python-watcherclient-doc/usr/.../html']):
… etc. Patch attached that sets "None" instead but retains the existing
fallback logic.
[0] https://reproducible-builds.org/
Please note that this was reported in the Debian tracker:
https://bugs.debian.org/960607
and that the fix was applied to the Debian package.
Change-Id: I502bb2d11d90ce4c46c14904a8c048ea824f11d5
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Ib952d51523684ba21b1247a0cef59ea5552ecdca
The docs requirements migrated to doc/requirements.txt
we need not install things from requirements.txt.
Change-Id: I31972595411d814700b6b51113827f438085170a
Switch to openstackdocstheme 2.2.0. Using
the version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Set openstackdocs_pdf_link to link to PDF file. Note that
the link to the published document only works on docs.openstack.org
where the PDF file is placed in the top-level html directory. The
site-preview places the PDF in a pdf directory.
Remove docs requirements from lower-constraints, they are not needed
during install or test but only for docs building.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I58edf52ff891328b14edecc9e6e990b34cb730b7
flake8 new release 3.8.0 added new checks and gate pep8
job start failing. hacking 3.0.1 fix the pinning of flake8 to
avoid bringing in a new version with new checks.
Though it is fixed in latest hacking but 2.0 and 3.0 has cap for
flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also
break the pep8 job if new check are added.
To avoid similar gate break in future, we need to bump the hacking min
version.
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html
Change-Id: I794bcf026f8c30d81c84b8c26e8b982b0e7b5b17
Now that we no longer support py27, we can use the standard library
unittest.mock module instead of the third party mock lib.
Change-Id: Idac937dd704ef11dfc33e197f7539e3f7a5feb92
Python 3.8 is now our highest level supported python runtime.
This updates the default tox target environments to swap out
py37 for py38 to make sure local development testing is
covering this version.
This does not impact zuul jobs in any way, nor prevent local
tests against py37. It just changes the default if none is
explicitly provided.
Change-Id: Iac6ba63153af308cd82f3d3a303ce4c3fead0a5f
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: Ia0db684e1c03231a93f71cab49cbbd4f23768dda
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
