Hmm I guess I'm confused then. The only way I've generated TAP in the past is by using Test:More either ok() or is() or something to test values. Given that the existing .t files don't return predictable values, the only thing I could test for would be the TAP output that the test cases contained within are producing.

How would running all of the .t files using TAP::Harness from within a .t file, rather than from the main script give me any different output?

The only way I can imagine getting a different output would be to run it something like this:

set SDTOUT to a file 
for each .t file
   run .t
   parse output file
   for each line do either:
      is(1,1,testcasename) or is(1,0,testcasename)
next file

[download]

What is is that you're suggesting?

In reply to Re^4: TAP question by emalossi
in thread TAP question by emalossi

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.