Hernan Martinez Foffani wrote: > > From: Neal Norwitz <neal@metaslash.com> > > I pulled it from where the sun don't shine. :-) > > I did a bunch of ls/grep/echo/... commands. > > Then post processed manually. > > > > It's not maintained anywhere. It would be great if there was > > a place to maintain/update it. Suggestions? > > > > I have another script which builds python with test-coverage > > and will tell you each line/function that doesn't get executed > > in case you get really bored. :-) > > I'm interested in those scripts. Are they available for the > public? Since I don't think most people care, I will mail you directly. If there are enough people that want the script, I'll send it to the mailing list also. > > There's only about 200 functions in Objects/*.c. > > That "200", is the aprox number of functions that don't have > a corresponding unittest? It's the # of C functions that were never called after running the entire regression test suite. > By the way, is there a simmilar package that do the same > thing (tell which line/function that doesn't get executed) > for pure python programs? I mean, something that can run > with the standard Python distrib. There's 2 modules I know of: http://manatee.mojam.com/~skip/python/trace.py http://www.garethrees.org/2001/12/04/python-coverage/coverage.py Neal
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