|Age||Commit message (Collapse)||Author|
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
Code-Review+2: Andreas Florath <firstname.lastname@example.org>
Code-Review+2: Stephanie Miller <email@example.com>
Workflow+1: Ian Wienand <firstname.lastname@example.org>
Submitted-at: Fri, 20 Jan 2017 00:13:31 +0000
A sanity check that cache-url does the right thing when presented
with the appropriate curl return codes. This change brings in the
test code for scripts from tripleo-image-elements, which needs to
be factored out into a place both projects can use it.
I'm stubbing out curl so we don't have a dep on curl in our unit
tests, and because I've seen some strange behavior out of curl in
the gate that caused random failures in this test.
Code-Review+2: Ghe Rivero <email@example.com>
Code-Review+2: Tomas Sedovic <firstname.lastname@example.org>
Workflow+1: Ben Nemec <email@example.com>
Code-Review+2: Jay Dobies <firstname.lastname@example.org>
Submitted-at: Thu, 02 Oct 2014 20:28:27 +0000
Approved+1: Devananda van der Veen <email@example.com>
Code-Review+2: Devananda van der Veen <firstname.lastname@example.org>
Code-Review+2: Arata Notsu <email@example.com>
Submitted-at: Fri, 14 Dec 2012 07:26:34 +0000