Zathura is a customizable document viewer. It provides a minimalistic interface and an interface that mainly focuses on keyboard interaction.

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

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

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

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

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

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.

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

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

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

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

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.

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

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.

Test::Requires checks to see if the module can be loaded. If this fails, then rather than failing tests this skips all tests.

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.

This module creates a Fake ShareDir for your modules for testing.

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

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.

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.