33

I'm wondering if it's possible to combine coverage.xml files into 1 file to see global report in HTML output.

I've got my unit/functional tests running as 1 command and integration tests as the second command. That means my coverage for unit/functional tests are overridden by unit tests.

That would be great if I had some solution for that problem, mainly by combining those files into 1 file.

oz123
  • 27,559
  • 27
  • 125
  • 187
tunarob
  • 2,768
  • 4
  • 31
  • 48

5 Answers5

33

I found a different solution. I used combine feature (read here) So I run my coverage like: coverage run -p and then I do coverage combine.

If you want to keep the old reports, you can use --keep.

That's all. It generates 1 combined report.

Johan
  • 342
  • 3
  • 14
tunarob
  • 2,768
  • 4
  • 31
  • 48
  • 3
    `coverage combine` will merge all `.coverage_*` files in a directory and create a combined `.coverage` file and delete the others. Only needed when merging different directories. – MortenB Feb 06 '18 at 10:51
  • 1
    With argument `--keep` the `.coverage_*` files are not removed. – dmcontador Dec 10 '21 at 08:09
  • Now, it replaces `.coverage.*` files (`.` instead of `_`) – Rafael Oct 19 '22 at 13:07
26

You can't combine .xml files, but you can combine the raw data files. Your workflow would look like this:

$ COVERAGE_FILE=.coverage_func coverage run the_functional_tests.py
$ COVERAGE_FILE=.coverage_inte coverage run the_integration_tests.py
$ coverage combine
$ coverage xml
Ned Batchelder
  • 364,293
  • 75
  • 561
  • 662
  • 1
    A caveat to `coverage combine` is that files are addressed by path, thus this works fine when coverage is collected and merged in the same directory, but requires extra steps if one step is performed remotely (e.g. in a container) where Python source paths are different. – Dima Tisnek Dec 04 '18 at 03:09
  • 2
    Coverage.py has a feature to specifically help with this: https://coverage.readthedocs.io/en/v4.5.x/config.html#paths This seems to be often missed by people. What can I do to make it more apparent? – Ned Batchelder Dec 04 '18 at 11:06
  • 1
    I followed above steps but getting error "No data to combine". The directory already have two files to combine ".coverage_ca" and ".coverage_test". – LOrD_ARaGOrN Jan 09 '19 at 06:35
  • @GauravKohli i tried other method. You can find my solution below. – LOrD_ARaGOrN Jul 29 '20 at 12:07
  • This does work when all the raw coverage files are in the same directory, with a couple of tweaks. First, you have to unset COVERAGE_FILE. Second, combine is expecting file names starting with ".coverage.". I was getting the "No data to combine" until I made those two changes. – Donald.McLean Mar 25 '22 at 16:11
21

You can achieve same result by using appending option. Suppose you ran the coverage on three python scripts.After first coverage use -a for appending.

coverage run first.py
coverage run -a second.py
coverage run -a third.py

Print the report

coverage report -m

Output:Report

Name             Stmts   Miss  Cover   Missing
----------------------------------------------
first.py           97      1    99%   95
second.py            1      0   100%
third.py            10      0   100%
----------------------------------------------
TOTAL               108      1    99%
LOrD_ARaGOrN
  • 3,884
  • 3
  • 27
  • 49
5

If your source code is in a directory called my_project, you can also do this if you have included pytest and pytest-cov in your virtual environment:

pytest --cov-report html --cov=my_project unit_tests
pytest --cov-report html --cov=my_project --cov-append functional_tests

The --cov-append will add the functional test coverage info to the coverage file that was created when you ran the unit tests.

the-kakfa-dude
  • 61
  • 1
  • 1
1

I had similar case where I had multiple packages and each of them had its tests and they were run using own testrunner. so I could combine all the coverage xml by following these steps.

  1. Indivisually generate the coverage report.
    You would need to naviagte to each package and generate the report in that package. This would create .coverage file. You can also add [run]parallel=True in your .coveragerc to create coverage file appended with machine name and processid.

  2. Aggregate all the reports.
    You need to copy all the .coverage files to for these packages to a seaparte folder. You might want to run a batch or sh script to copy all the coverage files.

  3. Run combine.
    Now naviagte tp the folder when you have all the report files and then run coverage combine. This will delete all the coverage files and combine it to one .coverage file. Now you can run coverage html and coverage xml.

Chandan Kumar
  • 1,066
  • 10
  • 16