Rick Fisk wrote:
Has anyone been successful with producing meaningful coverage reports
when the test files are in a non-standard location?
Any help would be appreciated.
If you make judicious use of the command-line options to cover, as well
as to Devel::Cover's own options, you can probably get to where you need
to go.
See attached. I use something like it to generate coverage stats for
the Parrot configuration and build tools. The options exclude most of
the files in which I am not interested.
http://thenceforward.net/parrot/coverage/configure-build/coverage.html
HTH
jimk
#!/bin/sh
SANDBOX=$1
COVERAGEDIR=/topdir/coverage/configure-build ;
PARROTDIR=/topdir/$SANDBOX;
echo "Performing coverage analysis on $PARROTDIR";
cd $PARROTDIR && \
cover -delete $COVERAGEDIR && \
PERL5OPT=-MDevel::Cover=-db,$COVERAGEDIR/ \
perl Configure.pl --test && \
cover $COVERAGEDIR \
-ignore_re 'Configure\.pl' \
-ignore_re '^t\/' \
-ignore_re '^\/usr\/local\/bin' \
-ignore_re '^\/tmp' \
-ignore_re '^lib\/(?!Parrot)' && \
chmod 0755 $COVERAGEDIR/
