[bind10-dev] targets for test coverage reporting?

[Michal 'vorner' Vaner]

Hello

On Fri, Oct 22, 2010 at 04:21:05AM -0500, Jeremy C. Reed wrote:
> 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?

I'm not sure if I'm answering the think you want me to, but as make check works
for both python and C++, I think it makes sense for make coverage to do as well,
so reusing them. At last it would seem more convenient for me to remember just
one name for all of it.

Thanks

Have a nice day

-- 
A nuclear war can ruin your whole day.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20101022/98e44580/attachment.bin>