This library provides functions to enable testing of files and directories. For instance, the file_ok helper can test whether the contents of a file is equal to a particular string.

This test module helps write unit tests which assert that the code under test reports metrics via Metrics::Any.

Test::Inter is another framework for writing test scripts, which offer the ability to access specific tests in a reasonably interactive fashion, primarily for debugging purposes. Much of the syntax is loosely inspired by Test::More.

When used in a test script Test::Distribution goes through all the modules in your distribution, checks their POD, checks that they compile successfully and checks that they all define a $VERSION. In addition, this module performs a number of tests on the distribution itself. It checks that the distributed files match the SIGNATURE file, if that file exists. It checks that the distribution is not missing any core description files. It also checks that the complete set of pre-requisite packages are listed in the Makefile.PL file.

Test::LeakTrace provides several functions that trace memory leaks. This module scans arenas, the memory allocation system, so it can detect any leaked SVs in given blocks.

This module provides some drop-in replacements for the string comparison functions of Test::More, but which are more suitable when you test against long strings.

Simple test harness which allows tests to be run and results automatically aggregated and output to STDOUT.

In situations where you have deep trees of classes, there is a common situation in which you test a module 4 or 5 subclasses down, which should follow the correct behaviour of not just the subclass, but of all the parent classes.

This should be done to ensure that the implementation of a subclass has not somehow ``broken'' the object's behaviour in a more general sense.

Test::Object is a testing package designed to allow you to easily test what you believe is a valid object against the expected behaviour of all of the classes in its inheritance tree in one single call.

Test::Filename provides functions to convert all path separators automatically.

Test::Class::Most provides some more convenience when using Test::Class.

Test::Manifest overrides the default test file order. Instead of running all of the t/*.t files in ASCII-betical order, it looks in the t/test_manifest file to find out which tests you want to run and the order in which you want to run them. It constructs the right value for the build system to do the right thing.

This module is primarily (but not exclusively) for use in test scripts: A block eval configurable and extensible but by default trapping STDOUT, STDERR, warnings, exceptions, would-be exit codes, and return values from boxed blocks of test code.

This package provides a rich set of tools, plugins, bundles, etc built upon the Test2 testing library.

This module contains a collection of acceptance tests for implementations of Future::IO.

Test::SharedFork is a utility module for Test::Builder. It makes fork(2) safe to use in test cases.

This module was created to enable test suites to test code at specific points in time. Specifically it overrides localtime, gmtime and time at compile time and then relies on the user supplying a mock time via set_relative_time, set_absolute_time or set_fixed_time to alter future calls to gmtime,time or localtime.

Test::NoTabs lets you check the presence of tabs in your perl code.

Test::Fatal is an alternative to the popular Test::Exception. It does much less, but should allow greater flexibility in testing exception-throwing code with about the same amount of typing.

Test::File provides a collection of test utilities for file attributes.

Test::MockObject allows you to create objects that conform to particular interfaces with very little code. You don't have to reimplement the behavior, just the input and the output.

This module causes any warnings during testing to be captured and stored. It automatically adds an extra test that will run when your script ends to check that there were no warnings. If there were any warnings, the test will fail and output diagnostics of where, when and what the warning was, including a stack trace of what was going on when it occurred.

Test::RunValgind checks weather Valgrind does not detect errors (such as memory leaks) in an arbitrary binary executable.

This module exports three test functions and four diff-style functions.

Test::Simple contains basic utilities for writing tests.