.\" 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 \
.\" ========================================================================
.IX Title "Test::Harness::Straps 3"
.TH Test::Harness::Straps 3 "2002-06-01" "perl v5.8.0" "Perl Programmers Reference Guide"
Test::Harness::Straps \- detailed analysis of test results
\& use Test::Harness::Straps;
\& my $strap = Test::Harness::Straps->new;
\& # Various ways to interpret a test
\& my %results = $strap->analyze($name, \e@test_output);
\& my %results = $strap->analyze_fh($name, $test_filehandle);
\& my %results = $strap->analyze_file($test_file);
\& my %total = $strap->total_results;
\& # Altering the behavior of the strap UNIMPLEMENTED
\& my $verbose_output = $strap->dump_verbose();
\& $strap->dump_verbose_fh($output_filehandle);
\&\fB\s-1THIS\s0 \s-1IS\s0 \s-1ALPHA\s0 \s-1SOFTWARE\s0\fR 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
analysis of the test results difficult for anything but a human. To
make it easier for programs to work with test results, we provide
Test::Harness::Straps. Instead of printing the results, straps
provide them as raw data. You can also configure how the tests are to
The interface is currently incomplete. \fIPlease\fR contact the author
if you'd like a feature added or something change or just have
.IX Subsection "Construction"
\& my $strap = Test::Harness::Straps->new;
.IX Subsection "Analysis"
\& my %results = $strap->analyze($name, \e@test_output);
Analyzes the output of a single test, assigning it the given \f(CW$name\fR for
use in the total report. Returns the \f(CW%results\fR of the test. See
@test_output should be the raw output from the test, including newlines.
\& my %results = $strap->analyze_fh($name, $test_filehandle);
Like \f(CW\*(C`analyze\*(C'\fR, but it reads from the given filehandle.
.IP "\fBanalyze_file\fR" 4
\& my %results = $strap->analyze_file($test_file);
Like \f(CW\*(C`analyze\*(C'\fR, but it runs the given \f(CW$test_file\fR and parses it's
results. It will also use that name for the total report.
The \f(CW%results\fR returned from \fIanalyze()\fR contain the following information:
\& 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
\& skip_all if the whole test was skipped, this will
\& ok number of tests which passed
\& (including todo and skips)
\& todo number of todo tests seen
\& bonus number of todo tests which
\& 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}[$test_num - 1] =
\& { ok => is the test considered ok?
\& actual_ok => did it literally say 'ok'?
\& name => name of the test (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.
See \fIexamples/mini_harness.plx\fR for an example of use.
Michael G Schwern <schwern@pobox.com>
projects / OpenSPARC-T2-DV / blob