Listen to your feelings ;-). The tests in t/ should test your code and not do the work of the code itself.

Tests should be an independent instance that declares your code as correct, even after you changed parts of it or it is run on a different platform or your operating system is a new version. The important word is "independent". In your example you would write a test to check whether a missing directory produces an error message. If this test fails you know that that line doesn't work anymore in your script

Note it makes not much sense adding tests to old applications, unless you plan to rewrite, enhance or refactor the application, or adapt it to new environments

In reply to Re: Using Test modules in production scripts by jethro
in thread Using Test modules in production scripts by xssnark

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.