Well, certainly take a long look at the regression tests in the Perl core. They're not in the best shape (I swear there are at least 5 different methods for doing the ok/not ok thing), but they are extremely thorough, and in general show the right ways to test things.

I don't think you'll find too many examples of different (separable) functionalities being tested together. I'm not sure I can think of a particularly easy or sensible way to do that. Would there really be no way of testing certain functionality without needing to test two objects together? I can't think of any example where a test in the core checks more than one distinct functionality at a time.

The general point of regression testing is to define functionality by testing the building blocks -- once you have the simple operations guaranteed, they'll fit together correctly.

Most important is maintaining the test suite. Any time you fix a bug, write a test for it. Any time you change functionality, write a test for it. Any time you add documentation, write a test to make sure that things are behaving the way that you're documenting them. In fact, that's a good way to start to fill out your test suite -- go through your documentation and write a test for everything you assert about your modules.

In reply to Re: Regression testing by dchetlin
in thread Regression testing by jplindstrom

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.