This module provides a few convenience methods for testing warning based code.

This module provides a collection of test utilities for directory attributes.

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

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

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

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 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 provides a test that checks all dependencies have been installed properly.

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

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 );

Test::Version checks to ensure that all modules have a version defined, and that the version is valid.

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

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.

Test::Simple contains basic utilities for writing tests.

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

Test::Needs allows you to skip test scripts if modules are not available. The requested modules will be loaded, and optionally have their versions checked. If the module is missing, the test script will be skipped. Modules that are found but fail to compile will exit with an error rather than skip.

If used in a subtest, the remainder of the subtest will be skipped.

Test::DistManifest provides a simple method of testing that a MANIFEST file matches its distribution.

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::Deep compares two structures by going through each level, ensuring that the values match, that arrays and hashes have the same elements and that references are blessed into the correct class. It also handles circular data structures without getting caught in an infinite loop.

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::Class::Most provides some more convenience when using Test::Class.

Test::Roo provides composable, reusable tests with roles.

This Perl module is intended to easily test network connectivity to non-local Internet resources before functional tests begin. If the sockets cannot connect to the specified hosts and ports, the exception is caught and reported, and the tests skipped.

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.