> 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 ##### comments? --Guido van Rossum (home page: http://dinsdale.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4