I concur with Corion that you need low-level tests to make sure each routine does what it should as well as end-to-end tests to make sure the pieces come together as you expect. For the latter, you might want to look into Apache::Test for which there is a tutorial here.

When I've been using Apache::Test recently for end-to-end testing, I've found it useful at times to override the final presentation phase of my web application. Instead of returning a text/html page with nicely formatted results, I return a text/plain response containing a YAML dump of the application's internal state. Obviously you also need to test that the formatted results work too, but a state dump makes it very easy to test actual vs expected results for a wide range of input values.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.