Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

How to get the path coverage (or lines of code executed) after running a perl test file

by perl_help26 (Beadle)
on Apr 16, 2014 at 15:11 UTC ( [id://1082523]=perlquestion: print w/replies, xml ) Need Help??

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

Hello Everyone, I wrote a test file using LWP::Simple. How can I know the path coverage of my test file or the lines of code being executed in my program? Is there an easy way? Preferably not with Devel::Cover since it just won't install using cpan!... (there's a test that's failing aeval_merge.t does anyone know why? Thank you...

Replies are listed 'Best First'.
Re: How to get the path coverage (or lines of code executed) after running a perl test file
by MidLifeXis (Monsignor) on Apr 16, 2014 at 15:50 UTC

    It looks like the latest version with successful tests across the board is 1.08. Perhaps an explicit installation of that until some of the latest test failures are resolved might work for you?

    --MidLifeXis

Re: How to get the path coverage (or lines of code executed) after running a perl test file
by toolic (Bishop) on Apr 16, 2014 at 15:18 UTC

      Sorry yes it's a typo ...I am trying to install Devel::Cover using cpan but there's a test that's just failing: aeval_merge.t Do you know why?

        Because you're installing version 1.11 on Windows. Apparently establishing cross-platform portability within DEV releases before making stable releases hasn't been a high priority for the past couple of releases of that module. Witness the CPAN smoke test reports.

        That's the short answer. The long answer involves looking at the source code for the failing tests, the source code of the module, and at the specific test(s) that are failing in an attempt to uncover why this is happening. Once you've got that, you can file a bug report and hope the author fixes it. But first it's probably worthwhile to look at the bug queue and see if this is already in progress or not.

        The easiest short-term solution is to install an earlier release. It looks like going back only as far as last month's release of 1.09 will restore Windows compatibility for you. The previous releases are still available on CPAN; http://search.cpan.org/~pjcj/Devel-Cover-1.09/, for example. If 1.09 doesn't work out, try 1.08. Hopefully this issue will be fixed soon.


        Dave

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: perlquestion [id://1082523]
Front-paged by Arunbear
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others avoiding work at the Monastery: (3)
As of 2024-03-28 17:57 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found