GNU Pem is a simple tool for tracking personal income and expenses. It operates from the command line and it stores its data in a basic text format in your home directory. It can easily print reports of your spending on different expenses via a basic search feature.

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.

Test::Output provides a simple interface for testing output sent to STDOUT or STDERR. A number of different utilities are included to try and be as flexible as possible to the tester.

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.

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

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.

Test::SharedFork is a utility module for Test::Builder. It makes fork(2) safe to use in test cases.

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.

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.

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.

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

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

Test::YAML is a subclass of Test::Base with YAML specific support.

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

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.

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

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

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

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

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

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.

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