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.

At some point or another, most programmers find they need to compare floating-point numbers for equality. The typical idiom is to test if the absolute value of the difference of the numbers is within a desired tolerance, usually called epsilon. This module provides such a function for use with Test::More.

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

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

Loading this plugin causes your tests to fail if there any warnings while they run. Each warning generates a new failing test and the warning content is outputted via diag.

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.

Testing code which forks is problematic because each test has a number associated with it. Coordinating the test number amongst the parent and child processes is complicated. Test::Fork provides a function to smooth over the complications.

This module provides a test that checks all dependencies have been installed properly.

Test::FailWarnings adds test failures if warnings are caught.

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

This module performs various checks on a module's Regexp::Pattern patterns.

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.

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.

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

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

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

Test::Simple contains basic utilities for writing tests.

There are a number of different situations (like testing caching code) where you want to want to do a number of tests, and then verify that some underlying subroutine deep within the code was called a specific number of times.

Test::SubCalls module provides a number of functions for doing testing in this way in association with your normal Test::More (or similar) test scripts.

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

The Test::WriteVariants module provides for the dynamic generation of tests in nested combinations of contexts.