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

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

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

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

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 Perl testing library focuses on testing and working with XPath expressions, most likely in the context of XML document processing.

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

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

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

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

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 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 …"

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::Version checks to ensure that all modules have a version defined, and that the version is valid.

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.

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

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.

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.

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.

Test::File::ShareDir is some low level plumbing to enable a distribution to perform tests while consuming its own share directories in a manner similar to how they will be once installed.

This module provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends.

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.