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

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

Test::Tester allows testing of test modules based on Test::Builder with a minimum of effort.

Test::Base gives a way to trivially write your own test framework base class. It concentrates on offering reusable data driven patterns, so that you can write tests with a minimum of code.

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::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 tests that commands given particular arguments result in particular outputs by way of the exit status word, standard output, and standard error.

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

This module was written to ensure that a META.yml file meets the specification.

Test::File::Contents provides functions for testing the contents of files.

The intent of the Test::Script module is to provide a series of basic tests for 80% of the testing you will need to do for scripts in the script (or bin as is also commonly used) paths of your Perl distribution.

This module is a collection of tests useful for dealing with UTF-8 strings in Perl. This module has two types of tests: The validity tests check if a string is valid and not corrupt, whereas the characteristics tests will check that string has a given set of characteristics.

This module adds a test to your Perl distribution which checks for pod coverage of all appropriate files.

Test::Memory::Cycle is built on top of Devel::Cycle to give you an easy way to check for these circular references.

use Test::Memory::Cycle;

my $object = new MyObject;
# Do stuff with the object.
memory_cycle_ok( $object );

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.

This Perl testing library focuses on testing and working with XPath expressions, most likely in the context of XML document processing.

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.

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.

Test::Simple contains basic utilities for writing tests.

Fennec ties together several testing related modules and enhances their functionality in ways you don't get loading them individually. Fennec::Lite takes a minimalist approach to do for Fennec what Mouse does for Moose.

Test::Requires checks to see if the module can be loaded. If this fails, then rather than failing tests this skips all tests.

Test::EOL lets you check for the presence of trailing whitespace and/or windows line endings in your perl code.

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

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.