Wy are you trying to replace one module with another? Sounds like a lot of work. Personally, when I mock something up, I try to minimize what I mock as much as possible to minimize altering the behavior. By limiting what I mock, I can know that at least the other code is getting tested.

But if you really do want to replace one module with another, so long as they present identical interfaces, it shouldn't be too hard. However, if the module exports anything, then you have a problem. You'll need to load it and mock everything before anything else loads it.

Cheers,
Ovid

New address of my CGI Course.

In reply to Re: Testing procedure: how to mock? by Ovid
in thread Testing procedure: how to mock? by thor

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.