I think I understand what you are doing. And it appears to me that an output that follows the natural time order of how the various routines are called would be best with an eye towards making each test as independent as possible from the other tests.

If a test fails, the developer will want to know a) if you can repeat it and then b)given that you can do that, can you repeat it with the smallest data set and number of dependencies possible? Hopefully the printout should be a really good starting place for (b). So if you are asking if it is ok to have "redundant" information in the output? I would say yes!

If some other person in some other department is running your tests, it is often a very good thing if he winds up with a contiguous set of text that can be snipped out and sent to you when "something goes wrong". So say if you run init(),test1(),init(),test2... Presumably init() does the same thing every time, but by repeating this information in the output, the sequence that caused the problem is all connected in a contiguous way. And I would prefer that over: here's what init() does and then way down in the printout, here's what test1(), test2() did.

In reply to Re^3: File dynamic write operations by Marshall
in thread File dynamic write operations by perlpal

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.