Ports 搜索

UUID::Random generates random uuid strings. It does not satisfy any of the points listed in RFC 4122 but the default format. If you need RFC compliant UUID strings have a look at Data::UUID.

Test::Timer implements a set of test primitives to test and assert test times from bodies of code.

Test::TinyMocker - a very simple tool to mock external modules Available method: * mock($module, $method_or_methods, $sub) * unmock($module, $method_or_methods) * method * methods * should

Test::Trap is primarily (but not exclusively) for use in test scripts: a block eval on steroids, configurable and extensible, but by default trapping (Perl) STDOUT, STDERR, warnings, exceptions, would-be exit codes, and return values from boxed blocks of test code. The values collected by the latest trap can then be queried or tested through a special trap object.

This framework is intended to support unit testing in an object-oriented development paradigm (with support for inheritance of tests etc.) and is derived from the JUnit testing framework for Java by Kent Beck and Erich Gamma.

This module's goal is to be a one stop shop for checking to see that your versions across your dist are sane.

A patch to Perl 5.005_55 by the author implements a core API for weak references. This module is a Perl-level interface to that API, allowing weak references to be created in Perl. A weak reference is just like an ordinary Perl reference except that it isn't included in the reference count of the thing referred to. This means that once all references to a particular piece of data are weak, the piece of data is freed and all the weak references are set to undef. This is particularly useful for implementing circular data structures without memory leaks or caches of objects.

`VCS' is an API for abstracting access to all version control systems from Perl code. This is achieved in a similar fashion to the `DBI' suite of modules. It comes with example CVS and RCS wrappers.

Test::Warn provides a few convenience methods for testing warning based code.

If you've ever tried to use Test::NoWarnings to confirm there are no warnings generated by your tests, combined with the convenience of done_testing to not have to declare a test count, you'll have discovered that these two features do not play well together, as the test count will be calculated before the warnings test is run, resulting in a TAP error. (See examples/test_nowarnings.pl in this distribution for a demonstration.) 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.