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.

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

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

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

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 creates a Fake ShareDir for your modules for testing.

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 tests that commands given particular arguments result in particular outputs by way of the exit status word, standard output, and standard error.

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

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

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 was written to ensure that a META.yml file meets the specification.

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::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::FailWarnings adds test failures if warnings are caught.

In situations where you have deep trees of classes, there is a common situation in which you test a module 4 or 5 subclasses down, which should follow the correct behaviour of not just the subclass, but of all the parent classes.

This should be done to ensure that the implementation of a subclass has not somehow ``broken'' the object's behaviour in a more general sense.

Test::Object is a testing package designed to allow you to easily test what you believe is a valid object against the expected behaviour of all of the classes in its inheritance tree in one single call.

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::TrailingSpace tests for trailing spaces in Perl source files.

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::YAML is a subclass of Test::Base with YAML specific support.

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.

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