I'd love to see you elaborate on alternative techniques. Testing is often seen as a chore, and in the shop I work in, the problem is a blatant lack of testing (especially automated). More productive testing strategies might help push testing among peers, and that would be a good thing.

Better ideas for more productive testing are always welcome to me, but I'm not sufficiently trained or smart enough to derive more productive testing strategies from what you've written so far. I do use Smart::Comments, which I think you've mentioned, a little, but probably not as effective as I could. Also, there must be more to your techniques than using that?

In reply to Re^3: Testing methodology, best practices and a pig in a hut. by stiller
in thread Testing methodology, best practices and a pig in a hut. by BrowserUk

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.