9 # Can't use Carp because it might cause use_ok() to accidentally succeed
10 # even though the module being used forgot to use Carp. Yes, this
13 my($file, $line) = (caller(1))[1,2];
14 warn @_, " at $file line $line\n";
20 use vars qw($VERSION @ISA @EXPORT %EXPORT_TAGS $TODO);
23 @EXPORT = qw(ok use_ok require_ok
24 is isnt like unlike is_deeply
28 eq_array eq_hash eq_set
35 my $Test = Test::Builder->new;
38 # 5.004's Exporter doesn't have export_to_level.
43 (undef) = shift; # redundant arg
44 my $callpkg = caller($level);
45 $pkg->export($callpkg, @_);
51 Test::More - yet another framework for writing test scripts
55 use Test::More tests => $Num_Tests;
57 use Test::More qw(no_plan);
59 use Test::More skip_all => $reason;
61 BEGIN { use_ok( 'Some::Module' ); }
62 require_ok( 'Some::Module' );
64 # Various ways to say "ok"
65 ok($this eq $that, $test_name);
67 is ($this, $that, $test_name);
68 isnt($this, $that, $test_name);
70 # Rather than print STDERR "# here's what went wrong\n"
71 diag("here's what went wrong");
73 like ($this, qr/that/, $test_name);
74 unlike($this, qr/that/, $test_name);
76 cmp_ok($this, '==', $that, $test_name);
78 is_deeply($complex_structure1, $complex_structure2, $test_name);
81 skip $why, $how_many unless $have_some_feature;
83 ok( foo(), $test_name );
84 is( foo(42), 23, $test_name );
90 ok( foo(), $test_name );
91 is( foo(42), 23, $test_name );
94 can_ok($module, @methods);
95 isa_ok($object, $class);
100 # Utility comparison functions.
101 eq_array(\@this, \@that);
102 eq_hash(\%this, \%that);
103 eq_set(\@this, \@that);
106 my @status = Test::More::status;
114 B<STOP!> If you're just getting started writing tests, have a look at
115 Test::Simple first. This is a drop in replacement for Test::Simple
116 which you can switch to once you get the hang of basic testing.
118 The purpose of this module is to provide a wide range of testing
119 utilities. Various ways to say "ok" with better diagnostics,
120 facilities to skip tests, test future features and compare complicated
121 data structures. While you can do almost anything with a simple
122 C<ok()> function, it doesn't provide good diagnostic output.
125 =head2 I love it when a plan comes together
127 Before anything else, you need a testing plan. This basically declares
128 how many tests your script is going to run to protect against premature
131 The preferred way to do this is to declare a plan when you C<use Test::More>.
133 use Test::More tests => $Num_Tests;
135 There are rare cases when you will not know beforehand how many tests
136 your script is going to run. In this case, you can declare that you
137 have no plan. (Try to avoid using this as it weakens your test.)
139 use Test::More qw(no_plan);
141 In some cases, you'll want to completely skip an entire testing script.
143 use Test::More skip_all => $skip_reason;
145 Your script will declare a skip with the reason why you skipped and
146 exit immediately with a zero (success). See L<Test::Harness> for
149 If you want to control what functions Test::More will export, you
150 have to use the 'import' option. For example, to import everything
151 but 'fail', you'd do:
153 use Test::More tests => 23, import => ['!fail'];
155 Alternatively, you can use the plan() function. Useful for when you
156 have to calculate the number of tests.
159 plan tests => keys %Stuff * 3;
161 or for deciding between running the tests at all:
164 if( $^O eq 'MacOS' ) {
165 plan skip_all => 'Test irrelevant on MacOS';
178 $Test->exported_to($caller);
182 foreach my $idx (0..$#plan) {
183 if( $plan[$idx] eq 'import' ) {
184 @imports = @{$plan[$idx+1]};
189 __PACKAGE__->_export_to_level(1, __PACKAGE__, @imports);
200 By convention, each test is assigned a number in order. This is
201 largely done automatically for you. However, it's often very useful to
202 assign a name to each test. Which would you rather see:
210 ok 4 - basic multi-variable
211 not ok 5 - simple exponential
212 ok 6 - force == mass * acceleration
214 The later gives you some idea of what failed. It also makes it easier
215 to find the test in your script, simply search for "simple
218 All test functions take a name argument. It's optional, but highly
219 suggested that you use it.
222 =head2 I'm ok, you're not ok.
224 The basic purpose of this module is to print out either "ok #" or "not
225 ok #" depending on if a given test succeeded or failed. Everything
228 All of the following print "ok" or "not ok" depending on if the test
229 succeeded or failed. They all also return true or false,
236 ok($this eq $that, $test_name);
238 This simply evaluates any expression (C<$this eq $that> is just a
239 simple example) and uses that to determine if the test succeeded or
240 failed. A true expression passes, a false one fails. Very simple.
244 ok( $exp{9} == 81, 'simple exponential' );
245 ok( Film->can('db_Main'), 'set_db()' );
246 ok( $p->tests == 4, 'saw tests' );
247 ok( !grep !defined $_, @items, 'items populated' );
249 (Mnemonic: "This is ok.")
251 $test_name is a very short description of the test that will be printed
252 out. It makes it very easy to find a test in your script when it fails
253 and gives others an idea of your intentions. $test_name is optional,
254 but we B<very> strongly encourage its use.
256 Should an ok() fail, it will produce some diagnostics:
258 not ok 18 - sufficient mucus
259 # Failed test 18 (foo.t at line 42)
261 This is actually Test::Simple's ok() routine.
266 my($test, $name) = @_;
267 $Test->ok($test, $name);
274 is ( $this, $that, $test_name );
275 isnt( $this, $that, $test_name );
277 Similar to ok(), is() and isnt() compare their two arguments
278 with C<eq> and C<ne> respectively and use the result of that to
279 determine if the test succeeded or failed. So these:
281 # Is the ultimate answer 42?
282 is( ultimate_answer(), 42, "Meaning of Life" );
285 isnt( $foo, '', "Got some foo" );
287 are similar to these:
289 ok( ultimate_answer() eq 42, "Meaning of Life" );
290 ok( $foo ne '', "Got some foo" );
292 (Mnemonic: "This is that." "This isn't that.")
294 So why use these? They produce better diagnostics on failure. ok()
295 cannot know what you are testing for (beyond the name), but is() and
296 isnt() know what the test was and why it failed. For example this
299 my $foo = 'waffle'; my $bar = 'yarblokos';
300 is( $foo, $bar, 'Is foo the same as bar?' );
302 Will produce something like this:
304 not ok 17 - Is foo the same as bar?
305 # Failed test 1 (foo.t at line 139)
307 # expected: 'yarblokos'
309 So you can figure out what went wrong without rerunning the test.
311 You are encouraged to use is() and isnt() over ok() where possible,
312 however do not be tempted to use them to find out if something is
315 # XXX BAD! $pope->isa('Catholic') eq 1
316 is( $pope->isa('Catholic'), 1, 'Is the Pope Catholic?' );
318 This does not check if C<$pope->isa('Catholic')> is true, it checks if
319 it returns 1. Very different. Similar caveats exist for false and 0.
320 In these cases, use ok().
322 ok( $pope->isa('Catholic') ), 'Is the Pope Catholic?' );
324 For those grammatical pedants out there, there's an C<isn't()>
325 function which is an alias of isnt().
342 like( $this, qr/that/, $test_name );
344 Similar to ok(), like() matches $this against the regex C<qr/that/>.
348 like($this, qr/that/, 'this is like that');
352 ok( $this =~ /that/, 'this is like that');
354 (Mnemonic "This is like that".)
356 The second argument is a regular expression. It may be given as a
357 regex reference (i.e. C<qr//>) or (for better compatibility with older
358 perls) as a string that looks like a regex (alternative delimiters are
359 currently not supported):
361 like( $this, '/that/', 'this is like that' );
363 Regex options may be placed on the end (C<'/that/i'>).
365 Its advantages over ok() are similar to that of is() and isnt(). Better
366 diagnostics on failure.
377 unlike( $this, qr/that/, $test_name );
379 Works exactly as like(), only it checks if $this B<does not> match the
391 cmp_ok( $this, $op, $that, $test_name );
393 Halfway between ok() and is() lies cmp_ok(). This allows you to
394 compare two arguments using any binary perl operator.
396 # ok( $this eq $that );
397 cmp_ok( $this, 'eq', $that, 'this eq that' );
399 # ok( $this == $that );
400 cmp_ok( $this, '==', $that, 'this == that' );
402 # ok( $this && $that );
403 cmp_ok( $this, '&&', $that, 'this || that' );
406 Its advantage over ok() is when the test fails you'll know what $this
410 # Failed test (foo.t at line 12)
415 It's also useful in those cases where you are comparing numbers and
416 is()'s use of C<eq> will interfere:
418 cmp_ok( $big_hairy_number, '==', $another_big_hairy_number );
429 can_ok($module, @methods);
430 can_ok($object, @methods);
432 Checks to make sure the $module or $object can do these @methods
433 (works with functions, too).
435 can_ok('Foo', qw(this that whatever));
437 is almost exactly like saying:
439 ok( Foo->can('this') &&
444 only without all the typing and with a better interface. Handy for
445 quickly testing an interface.
447 No matter how many @methods you check, a single can_ok() call counts
448 as one test. If you desire otherwise, use:
450 foreach my $meth (@methods) {
451 can_ok('Foo', $meth);
457 my($proto, @methods) = @_;
458 my $class= ref $proto || $proto;
461 my $ok = $Test->ok( 0, "$class->can(...)" );
462 $Test->diag(' can_ok() called with no methods');
467 foreach my $method (@methods) {
468 my $test = "'$class'->can('$method')";
469 local($!, $@); # don't interfere with caller's $@
470 # eval sometimes resets $!
471 eval $test || push @nok, $method;
475 $name = @methods == 1 ? "$class->can('$methods[0]')"
476 : "$class->can(...)";
478 my $ok = $Test->ok( !@nok, $name );
480 $Test->diag(map " $class->can('$_') failed\n", @nok);
487 isa_ok($object, $class, $object_name);
488 isa_ok($ref, $type, $ref_name);
490 Checks to see if the given $object->isa($class). Also checks to make
491 sure the object was defined in the first place. Handy for this sort
494 my $obj = Some::Module->new;
495 isa_ok( $obj, 'Some::Module' );
497 where you'd otherwise have to write
499 my $obj = Some::Module->new;
500 ok( defined $obj && $obj->isa('Some::Module') );
502 to safeguard against your test script blowing up.
504 It works on references, too:
506 isa_ok( $array_ref, 'ARRAY' );
508 The diagnostics of this test normally just refer to 'the object'. If
509 you'd like them to be more specific, you can supply an $object_name
510 (for example 'Test customer').
515 my($object, $class, $obj_name) = @_;
518 $obj_name = 'The object' unless defined $obj_name;
519 my $name = "$obj_name isa $class";
520 if( !defined $object ) {
521 $diag = "$obj_name isn't defined";
523 elsif( !ref $object ) {
524 $diag = "$obj_name isn't a reference";
527 # We can't use UNIVERSAL::isa because we want to honor isa() overrides
528 local($@, $!); # eval sometimes resets $!
529 my $rslt = eval { $object->isa($class) };
531 if( $@ =~ /^Can't call method "isa" on unblessed reference/ ) {
532 if( !UNIVERSAL::isa($object, $class) ) {
533 my $ref = ref $object;
534 $diag = "$obj_name isn't a '$class' it's a '$ref'";
538 WHOA! I tried to call ->isa on your object and got some weird error.
539 This should never happen. Please contact the author immediately.
546 my $ref = ref $object;
547 $diag = "$obj_name isn't a '$class' it's a '$ref'";
555 $ok = $Test->ok( 0, $name );
556 $Test->diag(" $diag\n");
559 $ok = $Test->ok( 1, $name );
573 Sometimes you just want to say that the tests have passed. Usually
574 the case is you've got some complicated condition that is difficult to
575 wedge into an ok(). In this case, you can simply use pass() (to
576 declare the test ok) or fail (for not ok). They are synonyms for
579 Use these very, very, very sparingly.
595 If you pick the right test function, you'll usually get a good idea of
596 what went wrong when it failed. But sometimes it doesn't work out
597 that way. So here we have ways for you to write your own diagnostic
598 messages which are safer than just C<print STDERR>.
604 diag(@diagnostic_message);
606 Prints a diagnostic message which is guaranteed not to interfere with
607 test output. Handy for this sort of thing:
609 ok( grep(/foo/, @users), "There's a foo user" ) or
610 diag("Since there's no foo, check that /etc/bar is set up right");
614 not ok 42 - There's a foo user
615 # Failed test (foo.t at line 52)
616 # Since there's no foo, check that /etc/bar is set up right.
618 You might remember C<ok() or diag()> with the mnemonic C<open() or
621 B<NOTE> The exact formatting of the diagnostic output is still
622 changing, but it is guaranteed that whatever you throw at it it won't
623 interfere with the test.
636 You usually want to test if the module you're testing loads ok, rather
637 than just vomiting if its load fails. For such purposes we have
638 C<use_ok> and C<require_ok>.
644 BEGIN { use_ok($module); }
645 BEGIN { use_ok($module, @imports); }
647 These simply use the given $module and test to make sure the load
648 happened ok. Its recommended that you run use_ok() inside a BEGIN
649 block so its functions are exported at compile-time and prototypes are
652 If @imports are given, they are passed through to the use. So this:
654 BEGIN { use_ok('Some::Module', qw(foo bar)) }
658 use Some::Module qw(foo bar);
664 my($module, @imports) = @_;
665 @imports = () unless @imports;
669 local($@,$!); # eval sometimes interferes with $!
673 $module->import(\@imports);
676 my $ok = $Test->ok( !$@, "use $module;" );
680 $Test->diag(<<DIAGNOSTIC);
681 Tried to use '$module'.
694 Like use_ok(), except it requires the $module.
703 local($!, $@); # eval sometimes interferes with $!
709 my $ok = $Test->ok( !$@, "require $module;" );
713 $Test->diag(<<DIAGNOSTIC);
714 Tried to require '$module'.
725 =head2 Conditional tests
727 Sometimes running a test under certain conditions will cause the
728 test script to die. A certain function or method isn't implemented
729 (such as fork() on MacOS), some resource isn't available (like a
730 net connection) or a module isn't available. In these cases it's
731 necessary to skip tests, or declare that they are supposed to fail
732 but will work in the future (a todo test).
734 For more details on the mechanics of skip and todo tests see
737 The way Test::More handles this is with a named block. Basically, a
738 block of tests which can be skipped over or made todo. It's best if I
746 skip $why, $how_many if $condition;
748 ...normal testing code goes here...
751 This declares a block of tests to skip, $how_many tests there are,
752 $why and under what $condition to skip them. An example is the
753 easiest way to illustrate:
756 skip "Pigs don't fly here", 2 unless Pigs->can('fly');
761 ok( $pig->altitude > 0, 'Pig is airborne' );
762 ok( $pig->airspeed > 0, ' and moving' );
765 If pigs cannot fly, the whole block of tests will be skipped
766 completely. Test::More will output special ok's which Test::Harness
767 interprets as skipped tests. Its important to include $how_many tests
768 are in the block so the total number of tests comes out right (unless
769 you're using C<no_plan>, in which case you can leave $how_many off if
772 Its perfectly safe to nest SKIP blocks.
774 Tests are skipped when you B<never> expect them to B<ever> pass. Like
775 an optional module is not installed or the operating system doesn't
776 have some feature (like fork() or symlinks) or maybe you need an
777 Internet connection and one isn't available.
779 You don't skip tests which are failing because there's a bug in your
780 program. For that you use TODO. Read on.
784 See L</Why are skip and todo so weird?>
790 my($why, $how_many) = @_;
792 unless( defined $how_many ) {
793 # $how_many can only be avoided when no_plan is in use.
794 _carp "skip() needs to know \$how_many tests are in the block"
795 unless $Test::Builder::No_Plan;
799 for( 1..$how_many ) {
811 local $TODO = $why if $condition;
813 ...normal testing code goes here...
816 Declares a block of tests you expect to fail and $why. Perhaps it's
817 because you haven't fixed a bug or haven't finished a new feature:
820 local $TODO = "URI::Geller not finished";
822 my $card = "Eight of clubs";
823 is( URI::Geller->your_card, $card, 'Is THIS your card?' );
826 URI::Geller->bend_spoon;
827 is( $spoon, 'bent', "Spoon bending, that's original" );
830 With a todo block, the tests inside are expected to fail. Test::More
831 will run the tests normally, but print out special flags indicating
832 they are "todo". Test::Harness will interpret failures as being ok.
833 Should anything succeed, it will report it as an unexpected success.
835 The nice part about todo tests, as opposed to simply commenting out a
836 block of tests, is it's like having a programmatic todo list. You know
837 how much work is left to be done, you're aware of what bugs there are,
838 and you'll know immediately when they're fixed.
840 Once a todo test starts succeeding, simply move it outside the block.
841 When the block is empty, delete it.
847 todo_skip $why, $how_many if $condition;
849 ...normal testing code...
852 With todo tests, its best to have the tests actually run. That way
853 you'll know when they start passing. Sometimes this isn't possible.
854 Often a failing test will cause the whole program to die or hang, even
855 inside an C<eval BLOCK> with and using C<alarm>. In these extreme
856 cases you have no choice but to skip over the broken tests entirely.
858 The syntax and behavior is similar to a C<SKIP: BLOCK> except the
859 tests will be marked as failing but todo. Test::Harness will
860 interpret them as passing.
865 my($why, $how_many) = @_;
867 unless( defined $how_many ) {
868 # $how_many can only be avoided when no_plan is in use.
869 _carp "todo_skip() needs to know \$how_many tests are in the block"
870 unless $Test::Builder::No_Plan;
874 for( 1..$how_many ) {
875 $Test->todo_skip($why);
885 =head2 Comparison functions
887 Not everything is a simple eq check or regex. There are times you
888 need to see if two arrays are equivalent, for instance. For these
889 instances, Test::More provides a handful of useful functions.
891 B<NOTE> These are NOT well-tested on circular references. Nor am I
892 quite sure what will happen with filehandles.
898 is_deeply( $this, $that, $test_name );
900 Similar to is(), except that if $this and $that are hash or array
901 references, it does a deep comparison walking each data structure to
902 see if they are equivalent. If the two structures are different, it
903 will display the place where they start differing.
905 Barrie Slaymaker's Test::Differences module provides more in-depth
906 functionality along these lines, and it plays well with Test::More.
908 B<NOTE> Display of scalar refs is not quite 100%
912 use vars qw(@Data_Stack);
913 my $DNE = bless [], 'Does::Not::Exist';
915 my($this, $that, $name) = @_;
918 if( !ref $this || !ref $that ) {
919 $ok = $Test->is_eq($this, $that, $name);
922 local @Data_Stack = ();
923 if( _deep_check($this, $that) ) {
924 $ok = $Test->ok(1, $name);
927 $ok = $Test->ok(0, $name);
928 $ok = $Test->diag(_format_stack(@Data_Stack));
940 foreach my $entry (@Stack) {
941 my $type = $entry->{type} || '';
942 my $idx = $entry->{'idx'};
943 if( $type eq 'HASH' ) {
944 $var .= "->" unless $did_arrow++;
947 elsif( $type eq 'ARRAY' ) {
948 $var .= "->" unless $did_arrow++;
951 elsif( $type eq 'REF' ) {
956 my @vals = @{$Stack[-1]{vals}}[0,1];
958 ($vars[0] = $var) =~ s/\$FOO/ \$got/;
959 ($vars[1] = $var) =~ s/\$FOO/\$expected/;
961 my $out = "Structures begin differing at:\n";
962 foreach my $idx (0..$#vals) {
963 my $val = $vals[$idx];
964 $vals[$idx] = !defined $val ? 'undef' :
965 $val eq $DNE ? "Does not exist"
969 $out .= "$vars[0] = $vals[0]\n";
970 $out .= "$vars[1] = $vals[1]\n";
979 eq_array(\@this, \@that);
981 Checks if two arrays are equivalent. This is a deep check, so
982 multi-level structures are handled correctly.
989 return 1 if $a1 eq $a2;
992 my $max = $#$a1 > $#$a2 ? $#$a1 : $#$a2;
994 my $e1 = $_ > $#$a1 ? $DNE : $a1->[$_];
995 my $e2 = $_ > $#$a2 ? $DNE : $a2->[$_];
997 push @Data_Stack, { type => 'ARRAY', idx => $_, vals => [$e1, $e2] };
998 $ok = _deep_check($e1,$e2);
999 pop @Data_Stack if $ok;
1012 # Quiet uninitialized value warnings when comparing undefs.
1019 if( UNIVERSAL::isa($e1, 'ARRAY') and
1020 UNIVERSAL::isa($e2, 'ARRAY') )
1022 $ok = eq_array($e1, $e2);
1024 elsif( UNIVERSAL::isa($e1, 'HASH') and
1025 UNIVERSAL::isa($e2, 'HASH') )
1027 $ok = eq_hash($e1, $e2);
1029 elsif( UNIVERSAL::isa($e1, 'REF') and
1030 UNIVERSAL::isa($e2, 'REF') )
1032 push @Data_Stack, { type => 'REF', vals => [$e1, $e2] };
1033 $ok = _deep_check($$e1, $$e2);
1034 pop @Data_Stack if $ok;
1036 elsif( UNIVERSAL::isa($e1, 'SCALAR') and
1037 UNIVERSAL::isa($e2, 'SCALAR') )
1039 push @Data_Stack, { type => 'REF', vals => [$e1, $e2] };
1040 $ok = _deep_check($$e1, $$e2);
1043 push @Data_Stack, { vals => [$e1, $e2] };
1055 eq_hash(\%this, \%that);
1057 Determines if the two hashes contain the same keys and values. This
1064 return 1 if $a1 eq $a2;
1067 my $bigger = keys %$a1 > keys %$a2 ? $a1 : $a2;
1068 foreach my $k (keys %$bigger) {
1069 my $e1 = exists $a1->{$k} ? $a1->{$k} : $DNE;
1070 my $e2 = exists $a2->{$k} ? $a2->{$k} : $DNE;
1072 push @Data_Stack, { type => 'HASH', idx => $k, vals => [$e1, $e2] };
1073 $ok = _deep_check($e1, $e2);
1074 pop @Data_Stack if $ok;
1084 eq_set(\@this, \@that);
1086 Similar to eq_array(), except the order of the elements is B<not>
1087 important. This is a deep check, but the irrelevancy of order only
1088 applies to the top level.
1092 # We must make sure that references are treated neutrally. It really
1093 # doesn't matter how we sort them, as long as both arrays are sorted
1094 # with the same algorithm.
1095 sub _bogus_sort { local $^W = 0; ref $a ? 0 : $a cmp $b }
1099 return 0 unless @$a1 == @$a2;
1101 # There's faster ways to do this, but this is easiest.
1102 return eq_array( [sort _bogus_sort @$a1], [sort _bogus_sort @$a2] );
1108 =head2 Extending and Embedding Test::More
1110 Sometimes the Test::More interface isn't quite enough. Fortunately,
1111 Test::More is built on top of Test::Builder which provides a single,
1112 unified backend for any test library to use. This means two test
1113 libraries which both use Test::Builder B<can be used together in the
1116 If you simply want to do a little tweaking of how the tests behave,
1117 you can access the underlying Test::Builder object like so:
1123 my $test_builder = Test::More->builder;
1125 Returns the Test::Builder object underlying Test::More for you to play
1131 return Test::Builder->new;
1139 Test::More is B<explicitly> tested all the way back to perl 5.004.
1141 =head1 BUGS and CAVEATS
1145 =item Making your own ok()
1147 If you are trying to extend Test::More, don't. Use Test::Builder
1150 =item The eq_* family has some caveats.
1152 =item Test::Harness upgrades
1154 no_plan and todo depend on new Test::Harness features and fixes. If
1155 you're going to distribute tests that use no_plan or todo your
1156 end-users will have to upgrade Test::Harness to the latest one on
1157 CPAN. If you avoid no_plan and TODO tests, the stock Test::Harness
1160 If you simply depend on Test::More, it's own dependencies will cause a
1161 Test::Harness upgrade.
1168 This is a case of convergent evolution with Joshua Pritikin's Test
1169 module. I was largely unaware of its existence when I'd first
1170 written my own ok() routines. This module exists because I can't
1171 figure out how to easily wedge test names into Test's interface (along
1172 with a few other problems).
1174 The goal here is to have a testing utility that's simple to learn,
1175 quick to use and difficult to trip yourself up with while still
1176 providing more flexibility than the existing Test.pm. As such, the
1177 names of the most common routines are kept tiny, special cases and
1178 magic side-effects are kept to a minimum. WYSIWYG.
1183 L<Test::Simple> if all this confuses you and you just want to write
1184 some tests. You can upgrade to Test::More later (its forward
1187 L<Test::Differences> for more ways to test complex data structures.
1188 And it plays well with Test::More.
1190 L<Test> is the old testing module. Its main benefit is that it has
1191 been distributed with Perl since 5.004_05.
1193 L<Test::Harness> for details on how your test results are interpreted
1196 L<Test::Unit> describes a very featureful unit testing interface.
1198 L<Test::Inline> shows the idea of embedded testing.
1200 L<SelfTest> is another approach to embedded testing.
1205 Michael G Schwern E<lt>schwern@pobox.comE<gt> with much inspiration
1206 from Joshua Pritikin's Test module and lots of help from Barrie
1207 Slaymaker, Tony Bowden, chromatic and the perl-qa gang.
1212 Copyright 2001 by Michael G Schwern E<lt>schwern@pobox.comE<gt>.
1214 This program is free software; you can redistribute it and/or
1215 modify it under the same terms as Perl itself.
1217 See F<http://www.perl.com/perl/misc/Artistic.html>