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);
181 foreach my $idx (0..$#plan) {
182 if( $plan[$idx] eq 'import' ) {
183 my($tag, $imports) = splice @plan, $idx, 2;
184 @imports = @$imports;
191 __PACKAGE__->_export_to_level(1, __PACKAGE__, @imports);
202 By convention, each test is assigned a number in order. This is
203 largely done automatically for you. However, it's often very useful to
204 assign a name to each test. Which would you rather see:
212 ok 4 - basic multi-variable
213 not ok 5 - simple exponential
214 ok 6 - force == mass * acceleration
216 The later gives you some idea of what failed. It also makes it easier
217 to find the test in your script, simply search for "simple
220 All test functions take a name argument. It's optional, but highly
221 suggested that you use it.
224 =head2 I'm ok, you're not ok.
226 The basic purpose of this module is to print out either "ok #" or "not
227 ok #" depending on if a given test succeeded or failed. Everything
230 All of the following print "ok" or "not ok" depending on if the test
231 succeeded or failed. They all also return true or false,
238 ok($this eq $that, $test_name);
240 This simply evaluates any expression (C<$this eq $that> is just a
241 simple example) and uses that to determine if the test succeeded or
242 failed. A true expression passes, a false one fails. Very simple.
246 ok( $exp{9} == 81, 'simple exponential' );
247 ok( Film->can('db_Main'), 'set_db()' );
248 ok( $p->tests == 4, 'saw tests' );
249 ok( !grep !defined $_, @items, 'items populated' );
251 (Mnemonic: "This is ok.")
253 $test_name is a very short description of the test that will be printed
254 out. It makes it very easy to find a test in your script when it fails
255 and gives others an idea of your intentions. $test_name is optional,
256 but we B<very> strongly encourage its use.
258 Should an ok() fail, it will produce some diagnostics:
260 not ok 18 - sufficient mucus
261 # Failed test 18 (foo.t at line 42)
263 This is actually Test::Simple's ok() routine.
268 my($test, $name) = @_;
269 $Test->ok($test, $name);
276 is ( $this, $that, $test_name );
277 isnt( $this, $that, $test_name );
279 Similar to ok(), is() and isnt() compare their two arguments
280 with C<eq> and C<ne> respectively and use the result of that to
281 determine if the test succeeded or failed. So these:
283 # Is the ultimate answer 42?
284 is( ultimate_answer(), 42, "Meaning of Life" );
287 isnt( $foo, '', "Got some foo" );
289 are similar to these:
291 ok( ultimate_answer() eq 42, "Meaning of Life" );
292 ok( $foo ne '', "Got some foo" );
294 (Mnemonic: "This is that." "This isn't that.")
296 So why use these? They produce better diagnostics on failure. ok()
297 cannot know what you are testing for (beyond the name), but is() and
298 isnt() know what the test was and why it failed. For example this
301 my $foo = 'waffle'; my $bar = 'yarblokos';
302 is( $foo, $bar, 'Is foo the same as bar?' );
304 Will produce something like this:
306 not ok 17 - Is foo the same as bar?
307 # Failed test (foo.t at line 139)
309 # expected: 'yarblokos'
311 So you can figure out what went wrong without rerunning the test.
313 You are encouraged to use is() and isnt() over ok() where possible,
314 however do not be tempted to use them to find out if something is
317 # XXX BAD! $pope->isa('Catholic') eq 1
318 is( $pope->isa('Catholic'), 1, 'Is the Pope Catholic?' );
320 This does not check if C<$pope->isa('Catholic')> is true, it checks if
321 it returns 1. Very different. Similar caveats exist for false and 0.
322 In these cases, use ok().
324 ok( $pope->isa('Catholic') ), 'Is the Pope Catholic?' );
326 For those grammatical pedants out there, there's an C<isn't()>
327 function which is an alias of isnt().
344 like( $this, qr/that/, $test_name );
346 Similar to ok(), like() matches $this against the regex C<qr/that/>.
350 like($this, qr/that/, 'this is like that');
354 ok( $this =~ /that/, 'this is like that');
356 (Mnemonic "This is like that".)
358 The second argument is a regular expression. It may be given as a
359 regex reference (i.e. C<qr//>) or (for better compatibility with older
360 perls) as a string that looks like a regex (alternative delimiters are
361 currently not supported):
363 like( $this, '/that/', 'this is like that' );
365 Regex options may be placed on the end (C<'/that/i'>).
367 Its advantages over ok() are similar to that of is() and isnt(). Better
368 diagnostics on failure.
379 unlike( $this, qr/that/, $test_name );
381 Works exactly as like(), only it checks if $this B<does not> match the
393 cmp_ok( $this, $op, $that, $test_name );
395 Halfway between ok() and is() lies cmp_ok(). This allows you to
396 compare two arguments using any binary perl operator.
398 # ok( $this eq $that );
399 cmp_ok( $this, 'eq', $that, 'this eq that' );
401 # ok( $this == $that );
402 cmp_ok( $this, '==', $that, 'this == that' );
404 # ok( $this && $that );
405 cmp_ok( $this, '&&', $that, 'this || that' );
408 Its advantage over ok() is when the test fails you'll know what $this
412 # Failed test (foo.t at line 12)
417 It's also useful in those cases where you are comparing numbers and
418 is()'s use of C<eq> will interfere:
420 cmp_ok( $big_hairy_number, '==', $another_big_hairy_number );
431 can_ok($module, @methods);
432 can_ok($object, @methods);
434 Checks to make sure the $module or $object can do these @methods
435 (works with functions, too).
437 can_ok('Foo', qw(this that whatever));
439 is almost exactly like saying:
441 ok( Foo->can('this') &&
446 only without all the typing and with a better interface. Handy for
447 quickly testing an interface.
449 No matter how many @methods you check, a single can_ok() call counts
450 as one test. If you desire otherwise, use:
452 foreach my $meth (@methods) {
453 can_ok('Foo', $meth);
459 my($proto, @methods) = @_;
460 my $class = ref $proto || $proto;
463 my $ok = $Test->ok( 0, "$class->can(...)" );
464 $Test->diag(' can_ok() called with no methods');
469 foreach my $method (@methods) {
470 local($!, $@); # don't interfere with caller's $@
471 # eval sometimes resets $!
472 eval { $proto->can($method) } || push @nok, $method;
476 $name = @methods == 1 ? "$class->can('$methods[0]')"
477 : "$class->can(...)";
479 my $ok = $Test->ok( !@nok, $name );
481 $Test->diag(map " $class->can('$_') failed\n", @nok);
488 isa_ok($object, $class, $object_name);
489 isa_ok($ref, $type, $ref_name);
491 Checks to see if the given $object->isa($class). Also checks to make
492 sure the object was defined in the first place. Handy for this sort
495 my $obj = Some::Module->new;
496 isa_ok( $obj, 'Some::Module' );
498 where you'd otherwise have to write
500 my $obj = Some::Module->new;
501 ok( defined $obj && $obj->isa('Some::Module') );
503 to safeguard against your test script blowing up.
505 It works on references, too:
507 isa_ok( $array_ref, 'ARRAY' );
509 The diagnostics of this test normally just refer to 'the object'. If
510 you'd like them to be more specific, you can supply an $object_name
511 (for example 'Test customer').
516 my($object, $class, $obj_name) = @_;
519 $obj_name = 'The object' unless defined $obj_name;
520 my $name = "$obj_name isa $class";
521 if( !defined $object ) {
522 $diag = "$obj_name isn't defined";
524 elsif( !ref $object ) {
525 $diag = "$obj_name isn't a reference";
528 # We can't use UNIVERSAL::isa because we want to honor isa() overrides
529 local($@, $!); # eval sometimes resets $!
530 my $rslt = eval { $object->isa($class) };
532 if( $@ =~ /^Can't call method "isa" on unblessed reference/ ) {
533 if( !UNIVERSAL::isa($object, $class) ) {
534 my $ref = ref $object;
535 $diag = "$obj_name isn't a '$class' it's a '$ref'";
539 WHOA! I tried to call ->isa on your object and got some weird error.
540 This should never happen. Please contact the author immediately.
547 my $ref = ref $object;
548 $diag = "$obj_name isn't a '$class' it's a '$ref'";
556 $ok = $Test->ok( 0, $name );
557 $Test->diag(" $diag\n");
560 $ok = $Test->ok( 1, $name );
574 Sometimes you just want to say that the tests have passed. Usually
575 the case is you've got some complicated condition that is difficult to
576 wedge into an ok(). In this case, you can simply use pass() (to
577 declare the test ok) or fail (for not ok). They are synonyms for
580 Use these very, very, very sparingly.
596 If you pick the right test function, you'll usually get a good idea of
597 what went wrong when it failed. But sometimes it doesn't work out
598 that way. So here we have ways for you to write your own diagnostic
599 messages which are safer than just C<print STDERR>.
605 diag(@diagnostic_message);
607 Prints a diagnostic message which is guaranteed not to interfere with
608 test output. Handy for this sort of thing:
610 ok( grep(/foo/, @users), "There's a foo user" ) or
611 diag("Since there's no foo, check that /etc/bar is set up right");
615 not ok 42 - There's a foo user
616 # Failed test (foo.t at line 52)
617 # Since there's no foo, check that /etc/bar is set up right.
619 You might remember C<ok() or diag()> with the mnemonic C<open() or
622 B<NOTE> The exact formatting of the diagnostic output is still
623 changing, but it is guaranteed that whatever you throw at it it won't
624 interfere with the test.
637 You usually want to test if the module you're testing loads ok, rather
638 than just vomiting if its load fails. For such purposes we have
639 C<use_ok> and C<require_ok>.
645 BEGIN { use_ok($module); }
646 BEGIN { use_ok($module, @imports); }
648 These simply use the given $module and test to make sure the load
649 happened ok. It's recommended that you run use_ok() inside a BEGIN
650 block so its functions are exported at compile-time and prototypes are
653 If @imports are given, they are passed through to the use. So this:
655 BEGIN { use_ok('Some::Module', qw(foo bar)) }
659 use Some::Module qw(foo bar);
661 don't try to do this:
664 use_ok('Some::Module');
666 ...some code that depends on the use...
667 ...happening at compile time...
672 BEGIN { use_ok('Some::Module') }
673 BEGIN { ...some code that depends on the use... }
679 my($module, @imports) = @_;
680 @imports = () unless @imports;
684 local($@,$!); # eval sometimes interferes with $!
688 '$module'->import(\@imports);
691 my $ok = $Test->ok( !$@, "use $module;" );
695 $Test->diag(<<DIAGNOSTIC);
696 Tried to use '$module'.
709 Like use_ok(), except it requires the $module.
718 local($!, $@); # eval sometimes interferes with $!
724 my $ok = $Test->ok( !$@, "require $module;" );
728 $Test->diag(<<DIAGNOSTIC);
729 Tried to require '$module'.
740 =head2 Conditional tests
742 Sometimes running a test under certain conditions will cause the
743 test script to die. A certain function or method isn't implemented
744 (such as fork() on MacOS), some resource isn't available (like a
745 net connection) or a module isn't available. In these cases it's
746 necessary to skip tests, or declare that they are supposed to fail
747 but will work in the future (a todo test).
749 For more details on the mechanics of skip and todo tests see
752 The way Test::More handles this is with a named block. Basically, a
753 block of tests which can be skipped over or made todo. It's best if I
761 skip $why, $how_many if $condition;
763 ...normal testing code goes here...
766 This declares a block of tests that might be skipped, $how_many tests
767 there are, $why and under what $condition to skip them. An example is
768 the easiest way to illustrate:
771 eval { require HTML::Lint };
773 skip "HTML::Lint not installed", 2 if $@;
775 my $lint = new HTML::Lint;
776 isa_ok( $lint, "HTML::Lint" );
778 $lint->parse( $html );
779 is( $lint->errors, 0, "No errors found in HTML" );
782 If the user does not have HTML::Lint installed, the whole block of
783 code I<won't be run at all>. Test::More will output special ok's
784 which Test::Harness interprets as skipped, but passing, tests.
785 It's important that $how_many accurately reflects the number of tests
786 in the SKIP block so the # of tests run will match up with your plan.
788 It's perfectly safe to nest SKIP blocks. Each SKIP block must have
789 the label C<SKIP>, or Test::More can't work its magic.
791 You don't skip tests which are failing because there's a bug in your
792 program, or for which you don't yet have code written. For that you
799 my($why, $how_many) = @_;
801 unless( defined $how_many ) {
802 # $how_many can only be avoided when no_plan is in use.
803 _carp "skip() needs to know \$how_many tests are in the block"
804 unless $Test::Builder::No_Plan;
808 for( 1..$how_many ) {
820 local $TODO = $why if $condition;
822 ...normal testing code goes here...
825 Declares a block of tests you expect to fail and $why. Perhaps it's
826 because you haven't fixed a bug or haven't finished a new feature:
829 local $TODO = "URI::Geller not finished";
831 my $card = "Eight of clubs";
832 is( URI::Geller->your_card, $card, 'Is THIS your card?' );
835 URI::Geller->bend_spoon;
836 is( $spoon, 'bent', "Spoon bending, that's original" );
839 With a todo block, the tests inside are expected to fail. Test::More
840 will run the tests normally, but print out special flags indicating
841 they are "todo". Test::Harness will interpret failures as being ok.
842 Should anything succeed, it will report it as an unexpected success.
843 You then know the thing you had todo is done and can remove the
846 The nice part about todo tests, as opposed to simply commenting out a
847 block of tests, is it's like having a programmatic todo list. You know
848 how much work is left to be done, you're aware of what bugs there are,
849 and you'll know immediately when they're fixed.
851 Once a todo test starts succeeding, simply move it outside the block.
852 When the block is empty, delete it.
858 todo_skip $why, $how_many if $condition;
860 ...normal testing code...
863 With todo tests, it's best to have the tests actually run. That way
864 you'll know when they start passing. Sometimes this isn't possible.
865 Often a failing test will cause the whole program to die or hang, even
866 inside an C<eval BLOCK> with and using C<alarm>. In these extreme
867 cases you have no choice but to skip over the broken tests entirely.
869 The syntax and behavior is similar to a C<SKIP: BLOCK> except the
870 tests will be marked as failing but todo. Test::Harness will
871 interpret them as passing.
876 my($why, $how_many) = @_;
878 unless( defined $how_many ) {
879 # $how_many can only be avoided when no_plan is in use.
880 _carp "todo_skip() needs to know \$how_many tests are in the block"
881 unless $Test::Builder::No_Plan;
885 for( 1..$how_many ) {
886 $Test->todo_skip($why);
893 =item When do I use SKIP vs. TODO?
895 B<If it's something the user might not be able to do>, use SKIP.
896 This includes optional modules that aren't installed, running under
897 an OS that doesn't have some feature (like fork() or symlinks), or maybe
898 you need an Internet connection and one isn't available.
900 B<If it's something the programmer hasn't done yet>, use TODO. This
901 is for any code you haven't written yet, or bugs you have yet to fix,
902 but want to put tests in your testing script (always a good idea).
907 =head2 Comparison functions
909 Not everything is a simple eq check or regex. There are times you
910 need to see if two arrays are equivalent, for instance. For these
911 instances, Test::More provides a handful of useful functions.
913 B<NOTE> These are NOT well-tested on circular references. Nor am I
914 quite sure what will happen with filehandles.
920 is_deeply( $this, $that, $test_name );
922 Similar to is(), except that if $this and $that are hash or array
923 references, it does a deep comparison walking each data structure to
924 see if they are equivalent. If the two structures are different, it
925 will display the place where they start differing.
927 Barrie Slaymaker's Test::Differences module provides more in-depth
928 functionality along these lines, and it plays well with Test::More.
930 B<NOTE> Display of scalar refs is not quite 100%
934 use vars qw(@Data_Stack);
935 my $DNE = bless [], 'Does::Not::Exist';
937 my($this, $that, $name) = @_;
940 if( !ref $this || !ref $that ) {
941 $ok = $Test->is_eq($this, $that, $name);
944 local @Data_Stack = ();
945 if( _deep_check($this, $that) ) {
946 $ok = $Test->ok(1, $name);
949 $ok = $Test->ok(0, $name);
950 $ok = $Test->diag(_format_stack(@Data_Stack));
962 foreach my $entry (@Stack) {
963 my $type = $entry->{type} || '';
964 my $idx = $entry->{'idx'};
965 if( $type eq 'HASH' ) {
966 $var .= "->" unless $did_arrow++;
969 elsif( $type eq 'ARRAY' ) {
970 $var .= "->" unless $did_arrow++;
973 elsif( $type eq 'REF' ) {
978 my @vals = @{$Stack[-1]{vals}}[0,1];
980 ($vars[0] = $var) =~ s/\$FOO/ \$got/;
981 ($vars[1] = $var) =~ s/\$FOO/\$expected/;
983 my $out = "Structures begin differing at:\n";
984 foreach my $idx (0..$#vals) {
985 my $val = $vals[$idx];
986 $vals[$idx] = !defined $val ? 'undef' :
987 $val eq $DNE ? "Does not exist"
991 $out .= "$vars[0] = $vals[0]\n";
992 $out .= "$vars[1] = $vals[1]\n";
1001 eq_array(\@this, \@that);
1003 Checks if two arrays are equivalent. This is a deep check, so
1004 multi-level structures are handled correctly.
1011 return 1 if $a1 eq $a2;
1014 my $max = $#$a1 > $#$a2 ? $#$a1 : $#$a2;
1016 my $e1 = $_ > $#$a1 ? $DNE : $a1->[$_];
1017 my $e2 = $_ > $#$a2 ? $DNE : $a2->[$_];
1019 push @Data_Stack, { type => 'ARRAY', idx => $_, vals => [$e1, $e2] };
1020 $ok = _deep_check($e1,$e2);
1021 pop @Data_Stack if $ok;
1034 # Quiet uninitialized value warnings when comparing undefs.
1041 if( UNIVERSAL::isa($e1, 'ARRAY') and
1042 UNIVERSAL::isa($e2, 'ARRAY') )
1044 $ok = eq_array($e1, $e2);
1046 elsif( UNIVERSAL::isa($e1, 'HASH') and
1047 UNIVERSAL::isa($e2, 'HASH') )
1049 $ok = eq_hash($e1, $e2);
1051 elsif( UNIVERSAL::isa($e1, 'REF') and
1052 UNIVERSAL::isa($e2, 'REF') )
1054 push @Data_Stack, { type => 'REF', vals => [$e1, $e2] };
1055 $ok = _deep_check($$e1, $$e2);
1056 pop @Data_Stack if $ok;
1058 elsif( UNIVERSAL::isa($e1, 'SCALAR') and
1059 UNIVERSAL::isa($e2, 'SCALAR') )
1061 push @Data_Stack, { type => 'REF', vals => [$e1, $e2] };
1062 $ok = _deep_check($$e1, $$e2);
1065 push @Data_Stack, { vals => [$e1, $e2] };
1077 eq_hash(\%this, \%that);
1079 Determines if the two hashes contain the same keys and values. This
1086 return 1 if $a1 eq $a2;
1089 my $bigger = keys %$a1 > keys %$a2 ? $a1 : $a2;
1090 foreach my $k (keys %$bigger) {
1091 my $e1 = exists $a1->{$k} ? $a1->{$k} : $DNE;
1092 my $e2 = exists $a2->{$k} ? $a2->{$k} : $DNE;
1094 push @Data_Stack, { type => 'HASH', idx => $k, vals => [$e1, $e2] };
1095 $ok = _deep_check($e1, $e2);
1096 pop @Data_Stack if $ok;
1106 eq_set(\@this, \@that);
1108 Similar to eq_array(), except the order of the elements is B<not>
1109 important. This is a deep check, but the irrelevancy of order only
1110 applies to the top level.
1112 B<NOTE> By historical accident, this is not a true set comparision.
1113 While the order of elements does not matter, duplicate elements do.
1117 # We must make sure that references are treated neutrally. It really
1118 # doesn't matter how we sort them, as long as both arrays are sorted
1119 # with the same algorithm.
1120 sub _bogus_sort { local $^W = 0; ref $a ? 0 : $a cmp $b }
1124 return 0 unless @$a1 == @$a2;
1126 # There's faster ways to do this, but this is easiest.
1127 return eq_array( [sort _bogus_sort @$a1], [sort _bogus_sort @$a2] );
1133 =head2 Extending and Embedding Test::More
1135 Sometimes the Test::More interface isn't quite enough. Fortunately,
1136 Test::More is built on top of Test::Builder which provides a single,
1137 unified backend for any test library to use. This means two test
1138 libraries which both use Test::Builder B<can be used together in the
1141 If you simply want to do a little tweaking of how the tests behave,
1142 you can access the underlying Test::Builder object like so:
1148 my $test_builder = Test::More->builder;
1150 Returns the Test::Builder object underlying Test::More for you to play
1156 return Test::Builder->new;
1164 Test::More is B<explicitly> tested all the way back to perl 5.004.
1166 Test::More is thread-safe for perl 5.8.0 and up.
1168 =head1 BUGS and CAVEATS
1172 =item Making your own ok()
1174 If you are trying to extend Test::More, don't. Use Test::Builder
1177 =item The eq_* family has some caveats.
1179 =item Test::Harness upgrades
1181 no_plan and todo depend on new Test::Harness features and fixes. If
1182 you're going to distribute tests that use no_plan or todo your
1183 end-users will have to upgrade Test::Harness to the latest one on
1184 CPAN. If you avoid no_plan and TODO tests, the stock Test::Harness
1187 If you simply depend on Test::More, it's own dependencies will cause a
1188 Test::Harness upgrade.
1195 This is a case of convergent evolution with Joshua Pritikin's Test
1196 module. I was largely unaware of its existence when I'd first
1197 written my own ok() routines. This module exists because I can't
1198 figure out how to easily wedge test names into Test's interface (along
1199 with a few other problems).
1201 The goal here is to have a testing utility that's simple to learn,
1202 quick to use and difficult to trip yourself up with while still
1203 providing more flexibility than the existing Test.pm. As such, the
1204 names of the most common routines are kept tiny, special cases and
1205 magic side-effects are kept to a minimum. WYSIWYG.
1210 L<Test::Simple> if all this confuses you and you just want to write
1211 some tests. You can upgrade to Test::More later (it's forward
1214 L<Test::Differences> for more ways to test complex data structures.
1215 And it plays well with Test::More.
1217 L<Test> is the old testing module. Its main benefit is that it has
1218 been distributed with Perl since 5.004_05.
1220 L<Test::Harness> for details on how your test results are interpreted
1223 L<Test::Unit> describes a very featureful unit testing interface.
1225 L<Test::Inline> shows the idea of embedded testing.
1227 L<SelfTest> is another approach to embedded testing.
1232 Michael G Schwern E<lt>schwern@pobox.comE<gt> with much inspiration
1233 from Joshua Pritikin's Test module and lots of help from Barrie
1234 Slaymaker, Tony Bowden, chromatic and the perl-qa gang.
1239 Copyright 2001 by Michael G Schwern E<lt>schwern@pobox.comE<gt>.
1241 This program is free software; you can redistribute it and/or
1242 modify it under the same terms as Perl itself.
1244 See F<http://www.perl.com/perl/misc/Artistic.html>