[TIP] Coverage combine with parallel mode
ned at nedbatchelder.com
Fri Nov 8 17:06:11 PST 2013
On 11/7/13 6:47 AM, christian.staffa at gmx.de wrote:
> Hi all :)
> I am a little confused and hope anyone on this list can help me...
> What is the aim:
> I will produce a coverage report with the coverage.py tool written by Ned Batchelder. The report should display the __relative__ pathes to the sources of the project like
> Whats the problem:
> The coverage is produced with the tool in parallel-mode due to the subprocess problem. The collecting of data is happen in the directory
> In the end of the measurement process all coverage data files (.coverage.xyz) are copied to a directory
> on the same machine.
> The coverage combine command is invoked to produce the report with the --rcfile=coveragerc option. The coveragerc contains a path section like
> source =
> BUT after the combine step the report is displaying the
> and not
> as intended.
> Is there a possibility with the path section of the configuration file to get rid of the absolute path prefixes generated in the report (/abspath/to/project)?
> Did i write the pathes section wrong for the combine step?
> Thanks for any help and clarify that :)
When the paths are remapped through the [paths] aliases, they result in
absolute paths, based on the first entry in the [paths] section. I see
your point though, relative might make more sense. But for example, the
XML report wants to have actual file paths so that the source can be
found when displaying in Jenkins.
Can you say more about why the full path is objectionable?
> (¸.·´.(¸.·` ¤chris¤
> ~#sent by iphone#~
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
More information about the testing-in-python