Test::CheckDeps adds a test that assures all dependencies have been
installed properly. If requested, it can bail out all testing on error.
Test Perl Classes the easy way
Test::Class provides a simple way of creating classes and
objects to test your code in an xUnit style.
Built using Test::Builder it is designing to work with
other Test::Builder based modules (Test::More,
Test::Differences, Test::Exception, etc.)
Note: This module will make more sense if you are already
familiar with the "standard" mechanisms for testing perl code.
Those unfamiliar with Test::Harness, Test::Simple, Test::More
and friends should go take a look at them now.
Note: This is an early release. Things may change. Be warned.
For many APIs with large numbers of classes, it can be very useful
to be able to do a quick once-over to make sure that classes,
methods, and inheritance is correct, before doing more comprehensive
testing. This module aims to provide such a capability.
Perl module to allow writing your unit tests in other modules than *.t
Test::CleanNamespaces 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.
Compare if the difference between two numbers is within a specified amount.
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.
The Test::Cmd module provides a low-level framework for portable automated
testing of executable commands and scripts (in any language, not just Perl),
especially commands and scripts that interact with the file system.
This test module is intended to simplify testing of external commands.
It does so by running the command under IPC::Open3, closing the stdin
immediately, and reading everything from the command's stdout and
stderr. It then makes the output available to be tested.
It is not (yet?) as feature-rich as Test::Cmd, but I think the interface
to this is much simpler. Tests also plug directly into the Test::Builder
framework, which plays nice with Test::More.
As compared to Test::Command, this module is simpler, relying on the
user to feed rc, stdout, and stderr to the appropriate other tests,
presumably in Test::More, but not necessarily.