I'm trying to figure out why the coverage reports I'm getting from
Devel::Cover (well, cover...) aren't recognizing the effects of most of my
testing. A simple example is one module for which Devel::Cover doesn't
record any subroutine coverage, yet I have tests for each of the subroutines
that run just fine. I put "use Devel::Cover"
Configuration particulars: Apache::Test qw(:withtestmore), mod_perl 1.29 (I
added "use Devel::Cover" to modperl_extra.pl" per instructions), apache
1.3.33, Devel::Cover 0.54, perl 5.8.6, fedora core 5. Oh - Module::Build.
I'm collecting coverage via ./Build testcover. (version control via
subversion, but I'll eat my hat if that's an issue)
I notice that the modules on which I'm using 'simpler tests' (as it were)
seem to be working-and-playing fine with Devel::Cover. Most of the tests,
though, are of the custom-request-and-response Apache::Test format - those
appear to be the ones Devel::Cover is missing.
I'm trapping and propagating errors (eval and die) - I wouldn't mention it
but that's another difference between the modules in which Devel::Cover
recognizes the testing and those in which it doesn't - the modules which
don't trap and propagate yield believable numbers.
I'd really love to use Devel::Cover - I love the effect mastering the
request/response Apache::Test framework has had on my code, and I really
want to start using code coverage as part of my toolkit.
Help?
Hilary
--
Hilary Holz http://acc.csueastbay.edu/~hholz/
Assistant Professor hilary.holz@xxxxxxxxxxxxxx
Dept of Mathematics and Computer Science
California State University, East Bay
|
