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.

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 some drop-in replacements for the string comparison functions of Test::More, but which are more suitable when you test against long strings.

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

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

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

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.

The Mock::Config Perl module allows temporarily setting and overriding Config values, even for the readonly XSConfig implementation as used in cperl. It does not store the mocked overrides lexically, just dynamically.

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

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::EOL lets you check for the presence of trailing whitespace and/or windows line endings 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.

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

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

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

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

This module provides routines for testing the exit status, standard output and standard error of external commands.

This module provides the most commonly used testing functions, along with automatically turning on strict and warning and gives a bit more fine-grained control over test suites.

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 creates a Fake ShareDir for your modules for testing.

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

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