markmoon,

Everyone here has given some great advice, but for me the testing lightbulb went off when I first really saw and messed around with an existsing test script. It was always too easy for me to put off reading tutorials and such (yes, the wrong kind of laziness), but when i finally got in front of a test that was already set up and ready to go, it all clicked. So in the spirit of passing on what worked for me, I have mocked up a quick test script that might help you get your feet wet.

First things first, you need to download and install the latest versions of Test::Simple (which has Test::More in it, which is your workhorse), and Test::Harness. You more than likely already have both on your system, but it can't hurt to get them up to date, and plus, Test::Harness comes with this great utility script called "prove", which makes running tests a lot simpler.

Now, here goes the code, it is purposely VERY simple so as not to cloud the issue, which is testing, with funky code.

Put this code into a file called "Module.pm"

package MyModule;

use strict;
use warnings;

sub add {
    my ($left, $right) = @_;
    return $left + $right;
}

1;

__END__
[download]

Put this code into a file called "test.t"

#!/usr/bin/perl

use strict;
use warnings;

# we have 3 tests to run
use Test::More tests => 3;
# if you dont know how many tests
# you have you can just replace:
#   tests => 3
# with:
#   "no_plan"
# that way you dont have to count 
# your tests, although when you are 
# finished its best to put the plan back 
# in place.

# test that we can require the module
require_ok("MyModule.pm");
# it also has the added benefit of requiring
# the actual module

# test that the module has the function "add" available
can_ok("MyModule", 'add');

# now test "add" works as expected
cmp_ok(MyModule::add(1, 1), '==', 2, '... 1 added to 1 is 2');
[download]

Now make sure both files (MyModule.pm and test.t) are in the same directory, and then run this from the command line (assuming you have already cd/chdir to the same directory).

prove test.t
[download]

You should see the following output:

test....ok                                                            
+       
All tests successful.
Files=1, Tests=3,  0 wallclock secs ( 0.15 cusr +  0.05 csys =  0.20 C
+PU)
[download]

And thats all. Obviously a more complex module would require a more complex tests, and take note, my tests are very simplistic. But this might give you help in getting started, as it helped me.

-stvn

---

---

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.