test coverage statistics

Ezra Peisach epeisach at MIT.EDU
Wed Dec 7 22:34:05 EST 2011

At one time - I modified valgrind to add a new function that would allow 
one to indicate how many mallocs before returning null... This was 
useful to iterate on the t_cc tests where it would set it to 2000 
mallocs, run the tests, reduce by one, run again, etc. - and see if 
could get down to one...  I fixed a number of failure cases that way.

I think I submitted it to the valgrind developers and will see if I can 
dig it up - but this could be one way
for testing the various failure cases - or some other controlled malloc 
failure case.  It would definitely test
error paths...


On 12/7/2011 11:10 AM, Zhanna Tsitkova wrote:
> Hi,
> I've compiled a test coverage report using GNU's gcov tool on Ubuntu.
> Please see http://k5wiki.kerberos.org/wiki/Test_coverage
> It may be useful for those who writes the new tests for or works on
> improving MIT Kerberos test suite.
> (More detail on generating this statistics can be found on http://web.mit.edu/tsitkova/www/build/krb_build/test_cov.html
>     )
> Thanks,
> Zhanna
> Zhanna Tsitkova
> tsitkova at mit.edu
> _______________________________________________
> krbdev mailing list             krbdev at mit.edu
> https://mailman.mit.edu/mailman/listinfo/krbdev

More information about the krbdev mailing list