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.

Check POD files for errors or warnings in a test file, using Pod::Simple to do the heavy lifting.

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

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

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.

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.

Test::Portability::Files module is used to check the portability across operating systems of the names of the files present in the distribution of a module. The tests use the advices given in 'Files and Filesystems' in perlport. The author of a distribution can select which tests to execute.

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

This module lets you check your module's namespaces for imported functions you might have forgotten to remove with namespace::autoclean or namespace::clean and are therefore available to be called as methods, which usually isn't want you want.

Test::More::UTF8 is a simple extension for the widely used Test::More module. By default, it will do a binmode :utf8 on all of Test::Builder's output handles thus enabling the easy use flagged strings without warnings like "Wide character in print …"

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

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

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

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.

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

Test::TrailingSpace tests for trailing spaces in Perl source files.

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 module provides routines for testing the exit status, standard output and standard error of external commands.

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

Testing code can involve making sure that files are created and deleted as expected. Doing this manually can be error prone, as it's easy to forget a file, or miss that some unexpected file was added. This module simplifies maintaining test directories by tracking their status as they are modified or tested with this API, making it simple to test both individual files, as well as to verify that there are no missing or unknown files.

Test::MockModule lets you temporarily redefine subroutines in other packages for the purposes of unit testing. A Test::MockModule object is set up to mock subroutines for a given module. The mocked object remembers the original subroutine so it can be easily restored. This happens automatically when all MockModule objects for the given module go out of scope, or when you unmock() the subroutine.

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::DistManifest provides a simple method of testing that a MANIFEST file matches its distribution.