package Foo;

## BEGIN UNIT TESTING
use Test::Unit;

print "Testing Foo: ";
create_suite();
run_suite();
print "\n\n";

sub test_new {
  my $foo = Foo->new(name => 'Bar', baz => "Quux");

  # Test to make sure it was constructed correctly.
  assert($foo->get_name() eq 'Bar');
  assert($foo->get_baz() eq 'Quux');

  # My constructor should die if called with no args, check for that w
+ith this line:
  eval { my $foo = Foo->new() };
  assert($@);
}

sub test_method_1 {
  my $foo = Foo->new(name => 'Bar', baz => 'foon');
  assert($foo->gurglify(15));
  assert($foo->gurgled_amount() == 15);
}
[download]

Unit Tests are definately a programmers friend. I wish I could give you more then one ++ for bringing this up. Lets just pretend that I gave you 2 ++ votes, and one vindictive -- vote for beating me to it. :-)

Seriously though, the only thing better then a unit test which covers all the methods and exercises all the code including error cases.... is a Perl script to run all those tests for you! After I make changes to a chunk of code, I run my tests with a single script, which tells me where all my blatant bugs are. Very useful indeed. (And gives you that nice warm feeling when the test passes)

quite true. i haven't used the Unit::Test - i end up rolling my own.

i'll have to look into it. . . :)