I found that writing tests along with the code helps me catch error conditions early. I use Test::More. Sometimes, the code I write is not intended to run in my development/test environment. In these cases I modify package objects, or data structures within the tests to get the desired scenario. Then I run a test against it.

Test::More example:

foo.pl contains a function named foo_plus_one like this -

     sub foo_plus_one($) { return $_[0]+1 }
[download]

You can 'require' your script into the test -

     BEGIN { require_ok("('foo.pl')") };
[download]

and call the functions -

     my $foo = 4;
     is( foo_plus_one($foo), '5', 'method foo_plus_one()' );
[download]

pass output -
1..1
ok 1 - method foo_plus_one()

OR fail -
1..1
not ok 1 - method foo_plus_one()
# Failed test (foo.t at line 6)
# got: '1003'
# expected: '5'


Testing is a great way to build a program! Ye-haw!

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	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.