Would you care to consider how many modules on CPAN predate "the standard" Test::Builder?

Or how many authors specify a plan?

I suppose that it would be labouring my point to suggest that of the output shown, only 1 line (the 4th) of the 7 is of any use to me at all, and that still tells me nothing about where the error occurred in the module being tested.

Good test descriptions help with this

With line numbers, I don't need to add test descriptions, good or bad. That's another piece of effort that it removes from the programmer.

Why force the programmer to translate the automatically assigned, automatically mainatained, unique identifier that a line number is, into a textual description that requires careful consideration to come up with a "good description", and force the tester (whether the original programmer, a maintanence programmer coming along later with a completely different mindset for who the original "good description" means absolutely nothing, or a user for whom it will probably never mean anything), back into a line number?

What purpose did all that extra effort serve?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^14: Self Testing Modules by BrowserUk
in thread Self Testing Modules by Sheol

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.