baf3ced0c3
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
17 lines
456 B
Plaintext
17 lines
456 B
Plaintext
# 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
|