This module adds a test to your Perl distribution which checks for pod coverage of all appropriate files.

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.

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.

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.

Tainted data is data that comes from an unsafe source, such as the command line, or, in the case of web apps, any GET or POST transactions. Read the perlsec man page for details on why tainted data is bad, and how to untaint the data.

When you're writing unit tests for code that deals with tainted data, you'll want to have a way to provide tainted data for your routines to handle, and easy ways to check and report on the taintedness of your data, in standard Test::More style.

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 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::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 warning based code.

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

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

Test::Class::Most provides some more convenience when using Test::Class.

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

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

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

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.

This module allows you to deliberately hide modules from a program even though they are installed. This is mostly useful for testing modules that have a fallback when a certain dependency module is not installed.

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

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.

This module is intended to be used as a drop-in replacement for Test::NoWarnings. It also adds an extra test, but runs this test before done_testing calculates the test count, rather than after. It does this by hooking into done_testing as well as via an END block. You can declare a plan, or not, and things will still Just Work.

Test::Memory::Cycle is built on top of Devel::Cycle to give you an easy way to check for these circular references.

use Test::Memory::Cycle;

my $object = new MyObject;
# Do stuff with the object.
memory_cycle_ok( $object );