.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.TH Test 3 "2002-06-01" "perl v5.8.0" "Perl Programmers Reference Guide"
Test \- provides a simple framework for writing test scripts
\& # use a BEGIN block so we print our plan before MyModule is loaded
\& BEGIN { plan tests => 14, todo => [3,4] }
\& ok(0); # ok, expected failure (see todo list, above)
\& ok(1); # surprise success!
\& ok(0,1); # failure: '0' ne '1'
\& ok('broke','fixed'); # failure: 'broke' ne 'fixed'
\& ok('fixed','fixed'); # success: 'fixed' eq 'fixed'
\& ok('fixed',qr/x/); # success: 'fixed' =~ qr/x/
\& ok(sub { 1+1 }, 2); # success: '2' eq '2'
\& ok(sub { 1+1 }, 3); # failure: '2' ne '3'
\& ok(0, int(rand(2)); # (just kidding :-)
\& ok @list, 3, "\e@list=".join(',',@list); #extra diagnostics
\& ok 'segmentation fault', '/(?i)success/'; #regex match
\& skip($feature_is_missing, ...); #do platform specific test
\&\fB\s-1STOP\s0!\fR If you are writing a new test, we \fIhighly suggest\fR you use
the new Test::Simple and Test::More modules instead.
Test::Harness expects to see particular output when it
executes tests. This module aims to make writing proper test scripts just
a little bit easier (and less error prone :\-).
.IX Subsection "Functions"
All the following are exported by Test by default.
\& BEGIN { plan %theplan; }
This should be the first thing you call in your test script. It
declares your testing plan, how many there will be, if any of them
should be allowed to fail, etc...
\& BEGIN { plan tests => 23 }
Things you can put in the plan:
\& tests The number of tests in your script.
\& This means all ok() and skip() calls.
\& todo A reference to a list of tests which are allowed
\& to fail. See L</TODO TESTS>.
\& onfail A subroutine reference to be run at the end of
\& the test script should any of the tests fail.
You must call \fIplan()\fR once and only once.
\& ok($have, $expect, $diagnostics);
This is the reason for Test's existance. Its the basic function that
handles printing \*(L"ok\*(R" or \*(L"not ok\*(R" along with the current test number.
In its most basic usage, it simply takes an expression. If its true,
the test passes, if false, the test fails. Simp.
\& ok( 1 + 1 == 2 ); # ok if 1 + 1 == 2
\& ok( $foo =~ /bar/ ); # ok if $foo contains 'bar'
\& ok( baz($x + $y) eq 'Armondo' ); # ok if baz($x + $y) returns
\& ok( @a == @b ); # ok if @a and @b are the same length
The expression is evaluated in scalar context. So the following will
\& ok( @stuff ); # ok if @stuff has any elements
\& ok( !grep !defined $_, @stuff ); # ok if everything in @stuff is
A special case is if the expression is a subroutine reference. In
that case, it is executed and its value (true or false) determines if
the test passes or fails.
In its two argument form it compares the two values to see if they
equal (with \f(CW\*(C`eq\*(C'\fR).
\& ok( "this", "that" ); # not ok, 'this' ne 'that'
If either is a subroutine reference, that is run and used as a
Should \f(CW$expect\fR either be a regex reference (ie. qr//) or a string that
looks like a regex (ie. '/foo/') \fIok()\fR will perform a pattern match
against it rather than using eq.
\& ok( 'JaffO', '/Jaff/' ); # ok, 'JaffO' =~ /Jaff/
\& ok( 'JaffO', qr/Jaff/ ); # ok, 'JaffO' =~ qr/Jaff/;
\& ok( 'JaffO', '/(?i)jaff/ ); # ok, 'JaffO' =~ /jaff/i;
Finally, an optional set of \f(CW$diagnostics\fR will be printed should the
test fail. This should usually be some useful information about the
test pertaining to why it failed or perhaps a description of the test.
\& ok( grep($_ eq 'something unique', @stuff), 1,
\& "Something that should be unique isn't!\en".
\& '@stuff = '.join ', ', @stuff
Unfortunately, a diagnostic cannot be used with the single argument
All these special cases can cause some problems. See \*(L"\s-1BUGS\s0 and \s-1CAVEATS\s0\*(R".
.IP "\(bu \s-1NORMAL\s0 \s-1TESTS\s0" 4
These tests are expected to succeed. If they don't something's
.IP "\(bu \s-1SKIPPED\s0 \s-1TESTS\s0" 4
Skip is for tests that might or might not be possible to run depending
on the availability of platform specific features. The first argument
should evaluate to true (think \*(L"yes, please skip\*(R") if the required
feature is not available. After the first argument, skip works
exactly the same way as do normal tests.
.IP "\(bu \s-1TODO\s0 \s-1TESTS\s0" 4
\&\s-1TODO\s0 tests are designed for maintaining an \fBexecutable \s-1TODO\s0 list\fR.
These tests are expected \s-1NOT\s0 to succeed. If a \s-1TODO\s0 test does succeed,
the feature in question should not be on the \s-1TODO\s0 list, now should it?
Packages should \s-1NOT\s0 be released with succeeding \s-1TODO\s0 tests. As soon
as a \s-1TODO\s0 test starts working, it should be promoted to a normal test
and the newly working feature should be documented in the release
\& BEGIN { plan test => 4, onfail => sub { warn "CALL 911!" } }
While test failures should be enough, extra diagnostics can be
triggered at the end of a test run. \f(CW\*(C`onfail\*(C'\fR is passed an array ref
of hash refs that describe each test failure. Each hash will contain
at least the following fields: \f(CW\*(C`package\*(C'\fR, \f(CW\*(C`repetition\*(C'\fR, and
\&\f(CW\*(C`result\*(C'\fR. (The file, line, and test number are not included because
their correspondence to a particular test is tenuous.) If the test
had an expected value or a diagnostic string, these will also be
The \fBoptional\fR \f(CW\*(C`onfail\*(C'\fR hook might be used simply to print out the
version of your package and/or how to report problems. It might also
be used to generate extremely sophisticated diagnostics for a
particularly bizarre test failure. However it's not a panacea. Core
dumps or other unrecoverable errors prevent the \f(CW\*(C`onfail\*(C'\fR hook from
running. (It is run inside an \f(CW\*(C`END\*(C'\fR block.) Besides, \f(CW\*(C`onfail\*(C'\fR is
probably over-kill in most cases. (Your test code should be simpler
than the code it is testing, yes?)
.IX Header "BUGS and CAVEATS"
\&\fIok()\fR's special handling of subroutine references is an unfortunate
\&\*(L"feature\*(R" that can't be removed due to compatibility.
\&\fIok()\fR's use of string eq can sometimes cause odd problems when comparing
numbers, especially if you're casting a string to a number:
\& ok( $foo, 1 ); # not ok, "1.0" ne 1
Your best bet is to use the single argument form:
\& ok( $foo == 1 ); # ok "1.0" == 1
\&\fIok()\fR's special handing of strings which look like they might be
regexes can also cause unexpected behavior. An innocent:
\& ok( $fileglob, '/path/to/some/*stuff/' );
will fail since Test.pm considers the second argument to a regex.
Again, best bet is to use the single argument form:
\& ok( $fileglob eq '/path/to/some/*stuff/' );
This module is no longer actively being developed, only bug fixes and
small tweaks (I'll still accept patches). If you desire additional
functionality, consider Test::More or Test::Unit.
Test::Simple, Test::More, Test::Harness, Devel::Cover
Test::Builder for building your own testing library.
Test::Unit is an interesting XUnit-style testing library.
Test::Inline and SelfTest let you embed tests in code.
Copyright (c) 1998\-2000 Joshua Nathaniel Pritikin. All rights reserved.
Copyright (c) 2001\-2002 Michael G Schwern.
Current maintainer, Michael G Schwern <schwern@pobox.com>
This package is free software and is provided \*(L"as is\*(R" without express
or implied warranty. It may be used, redistributed and/or modified
under the same terms as Perl itself.
projects / OpenSPARC-T2-DV / blob