[bind10-dev] targets for test coverage reporting?

[Jeremy C. Reed]

We currently have custom make targets of: clean-coverage, 
perform-coverage (aka make check), report-coverage, and coverage (does 
all three).

clean-coverage and report-coverage targets are for using the lcov tool 
for the c++ googletest tests.

My trac362 branch adds a python coverage too.

I will add targets for python: cleaning the coverage 
data and generating report.

In addition, I plan on making a target for the c++ code coverage and 
python code coverage that generates separate report for every single 
unit test file -- that way we can easier see if we inadvertently 
cover code.

Should I rename existing targets? Reuse existing? Use new name 
for python coverage for make targets?

Any thoughts on this?