Re: another benefit of one-liners

[Falkkin]

Of course, if you really want to test your objects, I'd recommend Test::Unit...

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);
}

... and so on. I typically use one single test for each method, along with a couple moe complicated tests that make sure the methods interact correctly. Run them all with perl Foo.pm every time you change anything within the file, and you can be assured that it all still works (as long as your tests are comprehensive...)

[Adam]

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)

[geektron]

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

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