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

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

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.

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

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

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.

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

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 contains a collection of acceptance tests for implementations of Future::IO.

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

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

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.

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

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.

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.

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

Test::RunValgind checks weather Valgrind does not detect errors (such as memory leaks) in an arbitrary binary executable.

This module is primarily (but not exclusively) for use in test scripts: A block eval configurable and extensible but by default trapping STDOUT, STDERR, warnings, exceptions, would-be exit codes, and return values from boxed blocks of test code.

Simple test harness which allows tests to be run and results automatically aggregated and output to STDOUT.

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.

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.

Using Test::PerlTidy, any file ending in .pl, .pm, .t or .PL will cause a test fail unless it is exactly as perltidy would like it to be.

Fennec ties together several testing related modules and enhances their functionality in ways you don't get loading them individually. Fennec::Lite takes a minimalist approach to do for Fennec what Mouse does for Moose.

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.