Herkum has asked for the wisdom of the Perl Monks concerning the following question:

I have a custom package that I am developing and I am running Build testcover to generate a Coverage report. I want to limit it to only the Modules that are a part of my package that I am bundling, but the coverage report covers all the modules that I am using as well.

What do I have to do in order to limit coverage to Modules in my package?

Replies are listed 'Best First'.
Re: Limited Coverage
by molecules (Monk) on Jan 21, 2010 at 20:02 UTC
[reply]
[d/l]

      Tried it, and the options I tried did not so I think I am missing something fundamental about how the options are supposed to work.

      Something that irks me about the whole situation, if you are integrating this into a package build, I would assume the default would be configured to check you package bundle, not everything.

[reply]
        Perhaps try invoking Devel::Cover a different way. I use the following commands and I've never seen it test anything outside of the directory in which I was working. 
        cover -delete
HARNESS_PERL_SWITCHES=-MDevel::Cover perl ./Build test
cover

        [download]
        Actually, what I really do is use a bash script: 
        #!/bin/bash
if [ -f Build.PL ]; then
    makecommand="perl ./Build"
elif [ -f Makefile.PL ]; then
    makecommand=make
else
    echo Cannot generate coverage information from this directory!
    exit 1
fi
cover -delete; HARNESS_PERL_SWITCHES=-MDevel::Cover $makecommand test;
+ cover

        [download]
        I wish I could help more, but I'm currently at the limit of my experience on this issue.

        Good luck.

[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom