> [snip - ah, helpful, now I understand how to use the testcover target]
:) > Devel::Cover is reporting > 100% statement coverage for a number of modules for which there are no tests > as of yet (legacy modules I have yet to revisit) I don't think that's unusual - D::C will aggregate all the results from all your tests into a single coverage report, so if that legacy code is hit _anywhere_ it will show up in the results. of course, it really depends on your situation, but I see this kind of "coverage bleeding" all the time. > while reporting that > subroutines for which I have tests are uncovered. did you click through the report html to find out what exactly isn't covered that you thought you did? are you absolutely certain that a condition was hit? also, try just running one test single test and see what happens. if you haven't noticed already, the D::C report shows how many times a statement was hit, as well as coverage statistics (which is in itself an incredible debugging aid :) so you should be able to track whether D::C is behaving properly given a small enough set of test code. or maybe you've already done all of this, so it's not much help. but my experience is that if I can get D::C to run under mod_perl without causing core dumps (which it does on occasion. work, that is) it tends to be accurate. --Geoff
