I've been a long-term user of test cases for my own code, as that gives me confidence that my code is good - or at the very least that changes I introduce haven't broken things too much!

My test-cases, in general, have been fairly straightforward in nature, and have worked without issues. As a matter of course I try to document the requirements of my code via a test case modules.t, which should ensure that anybody who can make the test case run successfully (via "make test") has all the modules required.

Here is an explicit example:

#!/usr/bin/perl -w -I..
#
#  Test that all the Perl modules we require are available.
#  (This list is automatically generated.)

use Test::More qw( no_plan );

# ...

BEGIN{ use_ok( 'CGI' ); }
require_ok( 'CGI' );

BEGIN{ use_ok( 'Date::Format' ); }
require_ok( 'Date::Format' );

BEGIN{ use_ok( 'POSIX' ); }
require_ok( 'POSIX' );

# ...
# ...

[download]

This test is part of a series which runs, via cron, on a daily basis. Unfortunately the combination of modules which I'm testing for give me a whole bunch of spam on STDERR:

skx@gold:~$ perl t.t > /dev/null
Subroutine main::ctime redefined at (eval 4) line 2
Prototype mismatch: sub main::ctime ($;$) vs none at (eval 4) line 2
Subroutine main::strftime redefined at (eval 4) line 2
Prototype mismatch: sub main::strftime ($\@;$) vs none at (eval 4) lin
+e 2
Subroutine main::asctime redefined at (eval 4) line 2
Prototype mismatch: sub main::asctime (\@;$) vs none at (eval 4) line 
+2

[download]

So, my question. Is it possible for me to avoid these errors whilst still working in the "standard" way when it comes to using Test::More and testing module availability?

(Certainly I accept that making my crontab entry throw away STDERR would solve my immediate problem, but it might hide things from me in the future.)

Steve
--

In reply to Issues when testing module loading by skx

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.