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...)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|