Chapter 5 of Perl Testing, A Developer's Notebook (O'Reilly: Ian Langworth and chromatic), "Testing Untestable Code" has a bit on over-riding the system() built-in with a vanilla Perl subroutine. You build a dispatch table in the subroutine to manage the commands you explicitly want to test, and make sure that the last lines of the table are:: 
} else {
    print("Un-handled command -- $the_command\n");
    return(-1);
}

[download]

Note to Ian and chromatic -- after reading your book I have come to the conclusion that there is **nothing** that is un-testable. You just have to look in the right chapter of PTaDN.... </code>

----
I Go Back to Sleep, Now.

OGB

In reply to Re: mocking or trapping system calls by Old_Gray_Bear
in thread mocking or trapping system calls by wu-lee

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.