Test::Harness::Straps - detailed analysis of test results

++

++

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 resu...

Test::Harness::Point - object for tracking a single test point

++

++

Test::Harness::Assert - simple assert

++

++

A simple assert routine since we don't have Carp::Assert handy. For internal use by Test::Harness ONLY!...

Test::Harness::Results - object for tracking results from a single test file

++

++

Test::Harness::Iterator - Internal Test::Harness Iterator

++

++

FOR INTERNAL USE ONLY! This is a simple iterator wrapper for arrays and filehandles. new() Create an iterator. next() Iterate through it, of course....

Test::Class - Easily create test classes in an xUnit/JUnit style

21 ++

21 ++

Test::Class provides a simple way of creating classes and objects to test your code in an xUnit style. Built using Test::Builder, it was designed to work with other Test::Builder based modules (Test::More, Test::Differences, Test::Exception, etc.). *...

Test::Harness - Run Perl standard test scripts with statistics

58 ++

58 ++

Although, for historical reasons, the Test::Harness distribution takes its name from this module it now exists only to provide TAP::Harness with an interface that is somewhat backwards compatible with Test::Harness 2.xx. If you're writing new code co...

Test::Run::Core - Base class to run standard TAP scripts.

++

++

Test::TAP::Model - DEPRECATED Use TAP::Harness, TAP::Formatter::HTML

1 ++

1 ++

This module is a subclass of Test::Harness::Straps (although in an ideal world it would really use delegation). It uses callbacks in the straps object to construct a deep structure, with all the data known about a test run accessible within. It's pur...

Test::Run::Core_GplArt - GPL/Artistic-licensed code of Test::Run::Core.

++

++

STOP! If all you want to do is write a test script, consider using Test::Simple. Test::Run::Core is the module that reads the output from Test::Simple, Test::More and other modules based on Test::Builder. You don't need to know about Test::Run::Core ...

Integrator::Test::TAP::Model::Patch - modified version of Test::TAP::Model

++

++

Test::TAP::Model::Consolidated - The unification of several Test::TAP::Model reports.

1 ++

1 ++

Test::TAP::Model::Consolidated is the same interface to Test::TAP::Model except that it provides an aggregate interface to result processing. Using it with the Test::Harness::Straps kind of methods will not work....