yardbirds team mailing list archive

[Space Hobo <spacehobo@xxxxxxxxxxxxx>]

I've pushed up revision 156, which bundles a statement coverage tool and
includes a script to drive it.  You can try running ./test_coverage in
your own checkouts, and see if it works for you.  I've tested it both on
hardy and karmic, so it ought to be fine.

The exit code is the number of modules that had incomplete coverage.

Once we reach 100% coverage I mean to release Anthropology and insist
from then on that all merges to trunk have both 100% test coverage and
no test failures. 

-- 
"Man, if everything were object-oriented then rsync
could do this already. Of course, if everything were
object-oriented I'd have a bushy moustache and be
wearing flares, which would suck." -- Sean Neakums