NAME
Test::Harness::Straps - detailed analysis of test results
SYNOPSIS
use Test::Harness::Straps;
my $strap = Test::Harness::Straps->new;
# Various ways to interpret a test
my %results = $strap->analyze($name, \@testoutput);
my %results = $strap->analyzefh($name, $testfilehandle);
my %results = $strap->analyzefile($testfile);
# UNIMPLEMENTED
my %total = $strap->totalresults;
# Altering the behavior of the strap UNIMPLEMENTED
my $verboseoutput = $strap->dumpverbose();
$strap->dumpverbosefh($outputfilehandle);
DESCRIPTION
TTHHIISS IISS AALLPPHHAA SSOOFFTTWWAARREE in that the interface is subject to change in
incompatible ways. It is otherwise stable.
Test::Harness is limited to printing out its results. This makes anal-
ysis of the test results difficult for anything but a human. To make
it easier for programs to work with test results, we provide Test::Har-
ness::Straps. Instead of printing the results, straps provide them as
raw data. You can also configure how the tests are to be run.
The interface is currently incomplete. Please contact the author if
you'd like a feature added or something change or just have comments.
CCOONNSSTTRRUUCCTTIIOONN
new()
my $strap = Test::Harness::Straps->new;
Initialize a new strap.
$$ssttrraapp->>iinniitt
$strap->init;
Initialize the internal state of a strap to make it ready for parsing.
AANNAALLYYSSIISS
$$ssttrraapp->>aannaallyyzzee(( $$nnaammee,, \\@@oouuttppuuttlliinneess ))
my %results = $strap->analyze($name, \@testoutput);
Analyzes the output of a single test, assigning it the given $name for
use in the total report. Returns the %results of the test. See
Results.
@testoutput should be the raw output from the test, including new-
lines.
$$ssttrraapp->>aannaallyyzzeeffhh(( $$nnaammee, $testfilehandle )
my %results = $strap->analyzefh($name, $testfilehandle);
Like "analyze", but it reads from the given filehandle.
$$ssttrraapp->>aannaallyyzzeeffiillee(( $$tteessttffiillee ))
my %results = $strap->analyzefile($testfile);
Like "analyze", but it runs the given $testfile and parses its
results. It will also use that name for the total report.
$$ssttrraapp->>ccoommmmaannddlliinnee(( $$ffiillee ))
Returns the full command line that will be run to test $file.
$$ssttrraapp->>command()
Returns the command that runs the test. Combine this with
"switches()" to build a command line.
Typically this is $^X, but you can set $ENV{HARNESSPERL} to use a dif-
ferent Perl than what you're running the harness under. This might be
to run a threaded Perl, for example.
You can also overload this method if you've built your own strap sub-
class, such as a PHP interpreter for a PHP-based strap.
$$ssttrraapp->>sswwiittcchheess(( $$ffiillee ))
Formats and returns the switches necessary to run the test.
$$ssttrraapp->>cclleeaanneeddsswwiittcchheess(( @@sswwiittcchheessffrroommuusseerr ))
Returns only defined, non-blank, trimmed switches from the parms
passed.
$$ssttrraapp->>IINNCC22PPEERRLL55LLIIBB
local $ENV{PERL5LIB} = $self->INC2PERL5LIB;
Takes the current value of @INC and turns it into something suitable
for putting onto "PERL5LIB".
$$ssttrraapp->>filteredINC()
my @filteredinc = $self->filteredINC;
Shortens @INC by removing redundant and unnecessary entries. Necessary
for OSes with limited command line lengths, like VMS.
$$ssttrraapp->>restorePERL5LIB()
$self->restorePERL5LIB;
This restores the original value of the "PERL5LIB" environment vari-
able. Necessary on VMS, otherwise a no-op.
PPaarrssiinngg
Methods for identifying what sort of line you're looking at.
""iissddiiaaggnnoossttiicc""
my $isdiagnostic = $strap->isdiagnostic($line, \$comment);
Checks if the given line is a comment. If so, it will place it into
$comment (sans #).
""iisshheeaaddeerr""
my $isheader = $strap->isheader($line);
Checks if the given line is a header (1..M) line. If so, it places how
many tests there will be in "$strap->{max}", a list of which tests are
todo in "$strap->{todo}" and if the whole test was skipped
"$strap->{skipall}" contains the reason.
""iissbbaaiilloouutt""
my $isbailout = $strap->isbailout($line, \$reason);
Checks if the line is a "Bail out!". Places the reason for bailing (if
any) in $reason.
""rreesseettffiilleessttaattee""
$strap->resetfilestate;
Resets things like "$strap->{max}" , "$strap->{skipall}", etc. so it's
ready to parse the next file.
RReessuullttss
The %results returned from "analyze()" contain the following informa-
tion:
passing true if the whole test is considered a pass
(or skipped), false if its a failure
exit the exit code of the test run, if from a file
wait the wait code of the test run, if from a file
max total tests which should have been run
seen total tests actually seen
skipall if the whole test was skipped, this will
contain the reason.
ok number of tests which passed
(including todo and skips)
todo number of todo tests seen
bonus number of todo tests which
unexpectedly passed
skip number of tests skipped
So a successful test should have max == seen == ok.
There is one final item, the details.
details an array ref reporting the result of
each test looks like this:
$results{details}[$testnum - 1] =
{ ok => is the test considered ok?
actualok => did it literally say 'ok'?
name => name of the test (if any)
diagnostics => test diagnostics (if any)
type => 'skip' or 'todo' (if any)
reason => reason for the above (if any)
};
Element 0 of the details is test #1. I tried it with element 1 being
#1 and 0 being empty, this is less awkward.
EEXXAAMMPPLLEESS
See examples/miniharness.plx for an example of use.
AUTHOR Michael G Schwern "", currently maintained by Andy
Lester "".
SEE ALSO
Test::Harness
perl v5.8.8 2001-09-21 Test::Harness::Straps(3pm)