[PATCH] Read line-by-line coverage data in the `python:coverage` tool.

[chirila.s.alexandru@…]

All the necessary implementations are already in place. This patch reads the annotated files from the coverdir and put's them into the report.

[chirila.s.alexandru@…]

Patch for build/pythontools that includes line by line coverage data in the report.

[osimons]

Looks good. Thanks! I see we provide this feature for both python:trace and python:figleaf tools, but not for python:coverage. It should indeed be supported, although as far as I can see the tool only supports 'executed' and 'missed' markings for each line. The simple '1' and '-' results of patch is therefore not quite up to par with the other tools that actually provide full line hit count.

Could you please add unit tests for the line-by-line data so that we also indirectly have documentation of the expected format and assurance that the code works. Just update bitten.build.tests.pythontools.CoverageTestCase with new methods as needed, and include in a refreshed patch.

[anonymous]

Replying to osimons:

The simple '1' and '-' results of patch is therefore not quite up to par with the other tools that actually provide full line hit count.

Unfortunately the coverage tool does not support this, and it will only tell if the line was hit or not, but not how many times :(

Could you please add unit tests for the line-by-line data so that we also indirectly have documentation of the expected format and assurance that the code works.

I'll be glad to do this.

[chirila.s.alexandru@…]

Patch for build/pythontools that includes line by line coverage data in the report, this also includes tests.

[anonymous]

I've added some tests for this functionality in the new patch. (all of which are passing)

~/bitten-trunk$ python bitten/build/tests/pythontools.py
...........No handlers could be found for logger "bitten.build.pythontools"
.................
----------------------------------------------------------------------
Ran 28 tests in 0.047s

OK

As I mentioned before, the ​coverage tool does not give the necessary information about the hit count, just 'executed' and 'missed'. This might make it a bit confusing when displaying the result, because it also displays 1 and 0 respectively.

Let me know if I can assist with anything else.

[osimons]

Thanks! Patch committed in [1022].

[osimons]

Follow-up fix for Windows tests committed in [1024].