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

oslotest>=1.10.0 # Apache-2.0
testrepository>=0.0.18 # Apache-2.0/BSD

# Doc requirements
sphinx!=1.3b1,<1.4,>=1.2.1 # BSD
oslosphinx>=4.7.0 # Apache-2.0

# releasenotes
reno>=1.8.0 # Apache-2.0

coverage>=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`
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
Updated from global requirements Change-Id: I45ed19e4333c37c8ea4943c344320e8a0a73c507 2015-08-25 07:06:43 +00:00			`oslotest>=1.10.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`
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: I0f152cb4160915bbcad273bca7d28f947b82eae4 2016-09-30 19:58:01 +00:00			`sphinx!=1.3b1,<1.4,>=1.2.1 # BSD`
			`oslosphinx>=4.7.0 # 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: Ib41e9cf05743c05fb299f84516d9179ea41e3f46 2016-11-02 15:31:00 +00:00			`reno>=1.8.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
			`coverage>=4.0 # Apache-2.0`