diskimage-builder/test-requirements.txt

# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
hacking<0.11,>=0.10.0
pylint==1.7.6;python_version=='2.7' # GPLv2
pylint;python_version>'3.0' #GPLv2

fixtures>=3.0.0 # Apache-2.0/BSD
mock>=2.0.0 # BSD
oslotest>=3.2.0 # Apache-2.0
testrepository>=0.0.18 # Apache-2.0/BSD
testtools>=2.2.0 # MIT

# Doc requirements
sphinx!=1.6.6,!=1.6.7,>=1.6.2 # BSD
openstackdocstheme>=1.18.1 # Apache-2.0

# releasenotes
reno>=2.5.0 # Apache-2.0

coverage!=4.4,>=4.0 # Apache-2.0
Updated from global requirements Change-Id: Ie2bb534b456ed3aac79b706cf51ecee9789527e4 2014-09-23 01:55:13 +00:00			`# The order of packages is significant, because pip processes them in the order`
			`# of appearance. Changing the order has an impact on the overall integration`
			`# process, which may cause wedges in the gate later.`
Updated from global requirements Change-Id: Iff075e25eeb091650ac85ca1e1af7a1fd3394d3e 2015-06-22 08:20:17 +00:00			`hacking<0.11,>=0.10.0`
Only cap pylint for python2 I noticed that pylint environment doesn't work with Python 3.7; I guess the pinned version has become incompatible. From the history the pin is only for Python 2.7 compatability, so just restrict it to that (with the basepython for the environment set to python3, it's questionable if we still support pylint with 2.7, but anyway). Change-Id: I6a916c8422239a4e1b47dcf28a4569f1637cae7a 2018-11-26 03:48:57 +00:00			`pylint==1.7.6;python_version=='2.7' # GPLv2`
			`pylint;python_version>'3.0' #GPLv2`
Fixed up test-requirements As a first step to OpenStack alignment, get test-requirements.txt in line with current OpenStack standard practices. Fixes: Bug #1205546 Change-Id: I899c3dc167df191b84008250671c58520c436a30 2013-07-27 02:27:45 +00:00
Add missing test requirements, fixup pylint env Add some missing test requirements. I noticed these because pylint was unhappy about the imports if you look closely. Also, pylint shouldn't be in deps as it comes from the parent's "test-requirements.txt" install. We don't need the VIRTUAL_ENV setting either. Change-Id: Ie082a058a9d3d51164448410a00d0719b0b37c4a 2017-06-05 00:25:49 +00:00			`fixtures>=3.0.0 # Apache-2.0/BSD`
Updated from global requirements Change-Id: Ic1d5fe9de580f445e88758e7adc279548ce87e5a 2017-08-24 11:37:04 +00:00			`mock>=2.0.0 # BSD`
Updated from global requirements Change-Id: I3e61c74abb3b4d69ca8d277c964d407c30315493 2018-01-17 20:31:03 +00:00			`oslotest>=3.2.0 # Apache-2.0`
Updated from global requirements Change-Id: I5229ba6b3d21f7902d1af847e0c567a0debedf7a 2016-01-22 04:03:13 +00:00			`testrepository>=0.0.18 # Apache-2.0/BSD`
Updated from global requirements Change-Id: I03dcd2a53ac16425dfa02ce67de4dd959d1bd53d 2017-11-16 11:01:41 +00:00			`testtools>=2.2.0 # MIT`
Create docs site containing element READMEs We currently do not have the ability to create a docs site which outlines all the elements. Change-Id: I77ccf61e0c4b1509b3e7ce9b8f15ea5ccfd50d9b 2015-02-07 10:30:02 +00:00
			`# Doc requirements`
Updated from global requirements Change-Id: I4f4ccdacc86caf9af77062786eed61a4adf7cd57 2018-03-15 06:52:03 +00:00			`sphinx!=1.6.6,!=1.6.7,>=1.6.2 # BSD`
Updated from global requirements Change-Id: I4495e8e78c5b1488ab4b8812db92c5da5ffc64d0 2018-01-24 00:51:49 +00:00			`openstackdocstheme>=1.18.1 # Apache-2.0`
Add releasenotes Use reno to start at keeping release notes. Add an initial log. Change-Id: Iba3ebd3b01c15030ac2585dda82e43657e511310 2016-03-14 03:29:28 +00:00
			`# releasenotes`
Updated from global requirements Change-Id: Ic1d5fe9de580f445e88758e7adc279548ce87e5a 2017-08-24 11:37:04 +00:00			`reno>=2.5.0 # Apache-2.0`
Fix coverage report There's a few things going on here Firstly, we need to install coverage tool in test-requirements Secondly, .testr.conf has to use PYTHON because the coverage report works by resetting PYTHON='coverage run ...' Thirdly, because we call ourselves diskimage-builder but the python module is diskimage_builder that seems to confuse things. We need to use "setup.py test" (note, that is different to "setup.py testr"!) to use the PBR testr wrapper. That exposes a --coverage-package-name argument that calls the coverage tool with the right argument. With this I got a coverage report for our unit tests Change-Id: I9012e18eb7d01bee035140e70afa76c47c27eb01 2017-01-18 04:07:46 +00:00
Updated from global requirements Change-Id: I27d0dbbc14a3d673d9449d0ed8a6f0c52e10257d 2017-05-15 00:42:53 +00:00			`coverage!=4.4,>=4.0 # Apache-2.0`