Seems like this is more about test planning than Perl, but that's OK by me...

demerphq has the right idea about groveling through the Perl delta and your own code, but there might be an easier way.

This'd be easier with a little more knowledge of the nature of the system under test, but I'll take a stab at two test methods you might consider. I'll assume (since it's Perl on Windows) that your production environment is small enough to be emulated in some way in a test environment.

The first approach: emulate your production environment in a test environment running 5.8. Duplicate the input to the production environment (or a subset of that input) and check for whatever's important: speed, data integrity, whatever.

The second approach: set up separate 5.6 and 5.8 test environments and send the same input through both environments. Compare the important stuff in each environment.

This kind of test planning is more art than science, but it may simply be enough to compare representative performance rather than plan particular tests. In any event, I for one am very interested in what you decide to do, and I hope to read more about your testing efforts.

Hope that helps...

In reply to Re: Perl migration testing by McMahon
in thread Perl migration testing by john7701

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.