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

This Perl module is intended to easily test network connectivity to non-local Internet resources before functional tests begin. If the sockets cannot connect to the specified hosts and ports, the exception is caught and reported, and the tests skipped.

This module is a collection of tests useful for dealing with UTF-8 strings in Perl. This module has two types of tests: The validity tests check if a string is valid and not corrupt, whereas the characteristics tests will check that string has a given set of characteristics.

This module provides a test that checks all dependencies have been installed properly.

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.

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.

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.

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

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

This module provides a few convenience methods for testing warning based code.

This module tests that commands given particular arguments result in particular outputs by way of the exit status word, standard output, and standard error.

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

Test::NoTabs lets you check the presence of tabs 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.

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

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

This module can test routines that manipulate random numbers by providing a known output from rand. Given a list of seeds with srand, it will return each in turn. After seeded random numbers are exhausted, it will always return 0. Seed numbers must be of a form that meets the expected output from rand as called with no arguments: they must be between 0 (inclusive) and 1 (exclusive). In order to facilitate generating and testing a nearly-one number, this module exports the function oneish, which returns a number just fractionally less than one.

When used in a test script Test::Distribution goes through all the modules in your distribution, checks their POD, checks that they compile successfully and checks that they all define a $VERSION. In addition, this module performs a number of tests on the distribution itself. It checks that the distributed files match the SIGNATURE file, if that file exists. It checks that the distribution is not missing any core description files. It also checks that the complete set of pre-requisite packages are listed in the Makefile.PL file.

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.

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.

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

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.

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.