[bind10-dev] targets for test coverage reporting?

[Jelte Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/22/2010 11:30 AM, Michal 'vorner' Vaner wrote:
> 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.
> 

yeah.

What about adding a 'python-coverage' target, renaming the current coverage
target to 'cpp-coverage', and making 'coverage' do both?

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzBWk0ACgkQ4nZCKsdOncXQiACgmEmeqYMTbsy09vXdnHpbJhZS
oBIAnR5eEXyLJjqq5sof138Wedmk4wHf
=Y0hN
-----END PGP SIGNATURE-----