I'm taking a roughly similar strategy now. Previously I had many of these:

is_xml $result, $expected, '... and we should receive the correct XML';

By generating $expected with a different algorithm (to ensure that I'm not just reaching into buggy code), I had to constantly maintain two different sets of code which did the same thing. It was very painful. Now I'm doing this:

is_well_formed_xml $result, '... and we should receive well-formed XML';

And to verify that it's correct, I'm adding more high-level integration testing. It's an annoying trade-off, but like what you're suggesting, it's a reasonable one.


New address of my CGI Course.

In reply to Re^2: When Test Suites Attack by Ovid
in thread When Test Suites Attack by Ovid

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":