Support python coverage

The python tool coverage is much more common and mainstream than pytest-cov (which requires non-standard pytest runner) see both pytest-cov stats and coverage stats

This means this plugin is not useful for projects not willing to use the non-standard pytest.

Please consider adding support for coverage.

[drettie]

The python coverage module already has a command to convert the .coverage file to html and cobertura compliant xml which then can be parse with this extension.

Here are the commands i run -

coverage run --branch -m unittest discover
coverage xml -o cov.xml
coverage html

I was quite confused getting this to work at first as the extension by default only searches for files named cov.xml whereas the default output filename from the coverage xml command is coverage.xml.

If for some reason you can’t rename the xml file there is also an option to change the default xml file in the extension settings.

@ryanluker might be worth adding coverage.xml as a default somewhere ?

[ryanluker]

@Josverl @ssbarnea Thanks for the spirited discussion, hopefully calmer heads have prevailed in the end. Just to give some input from myself, the plan is still to eventually provide support to coverage in milestone 3.0.0, but that is still a bit away and development on the extension is purely on a volunteer basis making it hard to give an expected timeline for this ticket.

We will continue to support what is laid out in the example python project (using the older setup) that is covered via integrations test to make sure that flow still can be used by python devs. Once the new coverage parser is developed, we will add this as a new option for python devs, while still supporting the older flow in the meantime as well.