in reply to Call for testers: File::Path

Skeeve$ perl Makefile.PL
WARNING: LICENSE is not a known parameter.
Checking if your kit is complete...
Looks good
'LICENSE' is not a known MakeMaker parameter name.
Writing Makefile for File::Path
Skeeve$ make
cp Path.pm blib/lib/File/Path.pm
Manifying blib/man3/File::Path.3pm
Skeeve$ make test
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_h
+arness(0, 'blib/lib', 'blib/arch')" t/*.t
t/Path.....ok 2/72# path separator on this platform is "/", updir is "
+.."    
t/Path.....ok                                                         
+       
        24/72 skipped: various reasons
t/taint....ok                                                         
+       
All tests successful, 24 subtests skipped.
Files=2, Tests=78,  1 wallclock secs ( 0.25 cusr +  0.10 csys =  0.35 
+CPU)

[download]
What now?
s$$([},&%#}/&/]+}%&{})*;#$&&s&&$^X.($'^"%]=\&(|?*{%
+.+=%;.#_}\&"^"-+%*).}%:##%}={~=~:.")&e&&s""`$''`"e

Replies are listed 'Best First'.
Re^2: Call for testers: File::Path
by grinder (Bishop) on May 27, 2007 at 21:52 UTC
    What now?

    Dunno. Here, have a ++.

    It's actually only failures I'm interested in. Other than that, no news is good news :)

    • another intruder with the mooring in the heart of the Perl

[reply]

      Thanks for the ++

      I thought you have some instruction in what to look. I never used the module and don't think I have a use for it at the moment. So if you want me to test some more on Mac, just tell me.

      BTW: What does it mean that 24 tests were skipped?

      s$$([},&%#}/&/]+}%&{})*;#$&&s&&$^X.($'^"%]=\&(|?*{%
      +.+=%;.#_}\&"^"-+%*).}%:##%}={~=~:.")&e&&s""`$''`"e
[reply]
[d/l]
[select]
        What does it mean that 24 tests were skipped?

        It just means that 24 of the tests were not conducted - and that it was the author's intention to not run those 24 tests for your specific operating system or build of perl.

        Cheers,
        Rob
[reply]

        Rob's explanation is correct. Here's the background:

        The question about the tests being skipped is that you have to run an extra setup step as root, in order to exercise some of the code paths that are hit when you just can't remove things because they don't belong to you, and you lack the privileges.

        It's there for mainly for improving the code coverage of the test suite, and just cannot be done in an automated fashion (e.g. "please type in root's password so that I can go and do stuff" is not gonna fly).

        • another intruder with the mooring in the heart of the Perl

[reply]

In Section Meditations