I differ with a co-worker on the output format of tests.

One of us believes that there should be just a minimum of status info, unless there is a problem. The theory is that the test should be run almost after every change to the code and their purpose is to quickly show off any problems

OK test 1 crankshaft turns 
OK test 2 spark plugs not fouled
OK test 3 gas in tank 
OK test 4 crankshaft turns with engine running 
****NOT OK**** test 5 muffler loose

[download]

The other one of us believes that it makes sense for the output of some tests to require a bit of eyeballing, that tests should be run less frequently and that the effort of making everything a boolean pass/fail isn't worth it. 

OK test 1 crankshaft still turns 
OK test 2 spark plugs not fouled
OK test 3 gas in tank 

Start ad-hoc tests...
There be 7 words in this line
This line should be red

[download]

Complicating things somewhat is that one of us believes this issue is largely a matter of taste and the other believes that this is a matter of right and wrong. (though not worth fighting about seriously)

So... who's right?

More generally, what is a method for figuring out what coding practices are a matter of taste and what are worth fighting about?

Appealing to authority, when the CPAN module upgrades itself, it is quite demonstrative....



email: mandog

In reply to Test output: Interpret or pass/fail by mandog

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.