[Python-Dev] barest beginnings of test coverage results

Guido van Rossum guido@beopen.com
Sat, 01 Jul 2000 08:21:12 -0500

> I compiled the Python interpreter with the flags necessary to get statement
> and branch coverage information then generated coverage files using the GNU
> coverage tool, gcov.  If you'd like a peek at the coverage files, have a
> look at
>     http://www.musi-cal.com/~skip/python/Python/dist/src/
> The statement/branch coverage information is for one run of executing
> Lib/test/regrtest.py.

Wow, Skip!  Very impressive.  But there's soooooo much data...  How do
we find the gems?  Should we just look at one file per day and try to
add testcases that get rid of the ##### comments?  Is there a way to
sort the files based on the number or significance of the #####

--Guido van Rossum (home page: http://dinsdale.python.org/~guido/)