[TIP] are the absolute paths in .coverage necessary?
Chris Withers
chris at simplistix.co.uk
Wed Oct 12 07:59:57 PDT 2016
What I currently have is:
[paths]
mylib =
mylib
/data/jenkins/jobs/mylib-test/workspace/PYTHON/*/mylib
tests =
tests
/data/jenkins/jobs/mylib-test/workspace/PYTHON/*/tests
How can I remove the absolute bits of that?
But, back to my original question: why are the paths in .coverage
absolute in the first place? :-)
Chris
On 12/10/2016 15:53, Ned Batchelder wrote:
> Chris, can you show the absolute paths you are using? I have this in my
> rc file to deal with varieties of CI:
>
> [paths]
> source =
> .
> *\coverage\trunk
> */coverage/trunk
> *\coveragepy
>
> --Ned.
>
>
> On 10/12/16 10:00 AM, Chris Withers wrote:
>> Hi Ned,
>>
>> Are the absolute paths necessary in .coverage?
>>
>> The reason I ask is that if, for example, they were relative to the
>> cwd, then I wouldn't need a .coveragerc with a whole bunch of paths
>> predicated on the exact filesystem layout of my CI server.
>>
>> thoughts?
>>
>> Chris
>
More information about the testing-in-python
mailing list