GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Test::TAP::Model::Subtest(3) User Contributed Perl Documentation Test::TAP::Model::Subtest(3)

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

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

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

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.

Whether the test is logically OK - if it's TODO and not OK this returns true.
This is the real value from the output. not OK and todo is false here.
The opposite of "ok"
The opposite of "actual_ok"
Whether the test was skipped
Whether the test was todo
Whether the result is consistent, that is OK xor TODO. An abnormal result should be noted.
The negation of "normal"
Whether this test is within the plan declared by the file.
Maybe it's in love with another fish.
The number of the test (useful for when the test came from a filtered query).
The raw line the data was parsed from.
Diagnosis immediately following the test line.
If there was a reason (for skip or todo), it's here.
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.

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

        (?:not )?ok $num/$planned
    
2008-01-02 perl v5.40.2

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.