Lately my downfall has been buggy test scripts.

• Wrong test count. I know there's a no_plan option, but that would leave me defenseless against
• Premature death of test script. Often the result of trying to exercise exceptions and error handlers. Yes, I know, the remedy is eval.
• Remembering how to use TODO and skip and skip_todo, or is that todo_skip? Finding out that skip if doesn't always protect a test script from tests that blow up, even though they're supposed to be skipped. See previous point.
• Testing exec.
• Forgetting to use diag for output, and printing something in a format that confuses the test harness.
• Testing subroutines and methods that print their own output.

It's still worth writing tests. Once I get a test to work, I can keep it around forever, and regression testing has saved me a lot of time over the years. I just wish there were a Test::Test module.

---

---

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.