יובל קוג'מן (Yuval Kogman) > Test-TAP-Model-0.10 > Test::TAP::Model::Subtest

Download:
Test-TAP-Model-0.10.tar.gz

Dependencies

Annotate this POD

CPAN RT

Open  0
View/Report Bugs
Source  

NAME ^

Test::TAP::Model::Subtest - An object for querying a test case

SYNOPSIS ^

        my @cases = $f->cases;
        $case[0]->ok; # or whatever

DESCRIPTION ^

This object allows you to ask questions about a test case in a test file's output.

METHODS ^

new

This constructor accepts the hash reference to the event logged for this subtest.

It doesn't bless the hash itself, but rather a reference to it, so that other objects' feet aren't stepped on.

ok
passed

Whether the test is logically OK - if it's TODO and not OK this returns true.

actual_ok

This is the real value from the output. not OK and todo is false here.

nok
failed

The opposite of ok

actual_nok

The opposite of actual_ok

skipped

Whether the test was skipped

todo

Whether the test was todo

normal

Whether the result is consistent, that is OK xor TODO. An abnormal result should be noted.

unexpected

The negation of normal

planned

Whether this test is within the plan declared by the file.

unplanned

Maybe it's in love with another fish.

num

The number of the test (useful for when the test came from a filtered query).

line

The raw line the data was parsed from.

diag

Diagnosis immediately following the test line.

reason

If there was a reason (for skip or todo), it's here.

pos
test_file
test_line
test_column

These methods extract the little <pos:file.t at line 5, column 3> comments as outputted by pugs' Test.pm.

Supposedly this is where the test case that fail was written.

str

A stringy representation much like Test::Harness prints in it's output:

        (?:not )?ok $num/$planned
syntax highlighting: