I'd be much more tempted to use a mock object for A when testing B. The mock object does nothing except provide the output you want for B.

Why is this useful? If you're only testing B with good output from A, what happens when B gets bad input? You haven't tested that if you're dependent on the real A providing data; you've only tested the "got good data" paths. Depending on the complexity of A's output and B's processing, this could leave a lot of code untested.

Since this has to do with actual money (and possible losses thereof) I'd want to make sure I had tested all the code paths.

In reply to Re: Passing data between modules using Test::Class by pemungkah
in thread Passing data between modules using Test::Class by arc_of_descent

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.