pyghmi/test-requirements.txt

hacking>=1.1.0,<1.2.0
coverage>=4.0
fixtures>=3.0.0
python-subunit>=1.0.0
sphinx>=1.6.5,<2.0.0;python_version=='2.7'  # BSD
sphinx>=1.6.5;python_version>='3.4'  # BSD
openstackdocstheme>=1.18.1 # Apache-2.0
stestr>=1.0.0 # Apache-2.0
testscenarios>=0.4
testtools>=2.2.0
oslotest>=3.2.0 # Apache-2.0
flake8-import-order>=0.13 # LGPLv3
Gate fix: Cap hacking to avoid gate failure hacking is not capped in g-r and it is in blacklist for requirement as hacking new version can break the gate jobs. Hacking can break gate jobs because of various reasons: - There might be new rule addition in hacking - Some rules becomes default from non-default - Updates in pycodestyle etc That was the main reason it was not added in g-r auto sync also. Most of the project maintained the compatible and cap the hacking version in test-requirements.txt and update to new version when project is ready. Bumping new version might need code fix also on project side depends on what new in that version. If project does not have cap the hacking version then, there is possibility of gate failure whenever new hacking version is released by QA team. Example of such failure in recent release of hacking 1.1.0 - http://lists.openstack.org/pipermail/openstack-dev/2018-May/130282.html Change-Id: I5f17ec6f67c7e7addfc5b2b2a3f17719402d9c0b 2018-10-16 11:43:37 +00:00			`hacking>=1.1.0,<1.2.0`
add lower-constraints Create a tox environment for running the unit tests against the lower bounds of the dependencies. Create a lower-constraints.txt to be used to enforce the lower bounds in those tests. Add openstack-tox-lower-constraints job to the zuul configuration. See [1] for details. 1. http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html Change-Id: I0f8b1bd44cd2f401593ce079cdecce5020807051 2018-05-16 15:18:13 +02:00			`coverage>=4.0`
			`fixtures>=3.0.0`
			`python-subunit>=1.0.0`
Update docs job Replace obsolete sphinx-build job with tox-docs job, use a template for this. The newer job uses "tox -e docs" directly. Add sphinx requirements for python 3. Change-Id: I1acc55a470ebacce812ba6840663302d759f69b7 2019-05-20 08:20:01 +02:00			`sphinx>=1.6.5,<2.0.0;python_version=='2.7' # BSD`
			`sphinx>=1.6.5;python_version>='3.4' # BSD`
Update package documentation * Switched to Sphinx openstacktheme * Rearranged docs along the OpenStack project lines * Add Sphinx docs building job * Added tox docs job Change-Id: I069d3a95b90bc798b1dcc0331d6e24a6c08d1317 2018-08-17 11:13:47 +02:00			`openstackdocstheme>=1.18.1 # Apache-2.0`
Switch to stestr According to OpenStack summit session [1], stestr is maintained project to which all OpenStack projects should migrate. Let's switch to stestr as other projects have already moved to it. Uses environment inclusions which need tox 2.8.1 due to a bug fix. So increase the tox minversion. [1] https://etherpad.openstack.org/p/YVR-python-pti Change-Id: If6eded0dd802cbdfe49ad72c64004585d4a1484b 2018-08-10 14:04:40 +02:00			`stestr>=1.0.0 # Apache-2.0`
Update from requirements Trying to remove usage of d2to1 - it can cause breakages. Also, had to fix hacking 102. Turns out it expects copyright headers in comments, not docstrings. Change-Id: I3494349ffe2d4cba9c8bcb73408d60bbc12eff5e 2013-09-13 11:21:12 -05:00			`testscenarios>=0.4`
add lower-constraints Create a tox environment for running the unit tests against the lower bounds of the dependencies. Create a lower-constraints.txt to be used to enforce the lower bounds in those tests. Add openstack-tox-lower-constraints job to the zuul configuration. See [1] for details. 1. http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html Change-Id: I0f8b1bd44cd2f401593ce079cdecce5020807051 2018-05-16 15:18:13 +02:00			`testtools>=2.2.0`
			`oslotest>=3.2.0 # Apache-2.0`
Use flake8 for testing Start using flake8 for style guide enforcement. Change-Id: I9d7c89498c10e682acf0f75bad20dfd4bb6152b5 2019-12-17 14:57:16 +01:00			`flake8-import-order>=0.13 # LGPLv3`