Modified items

All recently modified items, latest first.

perl-Test-Script-1.07-12.fc19.noarch: The intent of this module is to provide a series of basic tests for scripts in the bin directory of your Perl distribution.

perl-Test-Requires-0.08-1.lbn19.noarch: Test::Requires checks to see if the module can be loaded. If this fails, rather than failing tests this skips all tests.

perl-Test-Refcount-0.07-8.fc19.noarch: The Perl garbage collector uses simple reference counting during the normal execution of a program. This means that cycles or unweakened references in other parts of code can keep an object around for longer than intended. To help avoid this problem, the reference count of a new object from its class constructor ought to be 1. This way, the caller can know the object will be properly DESTROYed when it drops all of its references to it.

perl-Test-Portability-Files-0.06-1.lbn19.noarch: This 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 advice given in "Files and Filesystems" in perlport. The author of a distribution can select which tests to execute.

perl-Test-Pod-No404s-0.01-5.fc19.noarch: This module looks for any HTTP(S) links in your POD and verifies that they will not return a 404. It uses LWP::UserAgent for the heavy lifting, and simply lets you know if it failed to retrieve the document. More specifically, it uses $response->is_error as the "test".

perl-Test-Pod-LinkCheck-0.007-5.fc19.noarch: This module looks for any links in your POD and verifies that they point to a valid resource. It uses the Pod::Simple parser to analyze the pod files and look at their links. In a nutshell, it looks for L<Foo> links and makes sure that Foo exists. It also recognizes section links, L</SYNOPSIS> for example. Also, manual pages are resolved and checked.

perl-Test-Pod-Coverage-1.08-19.lbn19.noarch: Checks for POD coverage in files for your distribution.

perl-Test-Pod-1.46-1.lbn19.noarch: Check POD files for errors or warnings in a test file, using Pod::Simple to do the heavy lifting.

perl-Test-Perl-Critic-1.02-10.fc19.noarch: Test::Perl::Critic wraps the Perl::Critic engine in a convenient subroutine suitable for test programs written using the Test::More framework. This makes it easy to integrate coding-standards enforcement into the build process. For ultimate convenience (at the expense of some flexibility), see the criticism pragma.

perl-Test-Output-1.01-7.fc19.noarch: 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.

perl-Test-NoWarnings-1.04-2.lbn19.noarch: In general, your tests shouldn't produce warnings. This module causes any warnings 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 give a "not ok" and diagnostics of where, when and what the warning was, including a stack trace of what was going on when the it occurred.

perl-Test-NoTabs-1.3-5.lbn19.noarch: This module scans your project/distribution for any perl files (scripts, modules, etc.) for the presence of tabs.

perl-Test-Mouse-1.05-1.fc19.x86_64: This module provides some useful test functions for Mouse based classes. It is an experimental first release, so comments and suggestions are very welcome.

perl-Test-Moose-2.0802-1.fc19.x86_64: This module provides some useful test functions for Moose based classes. It is an experimental first release, so comments and suggestions are very welcome.

perl-Test-MockObject-1.20120301-2.fc19.noarch: Test::MockObject is a highly polymorphic testing object, capable of looking like all sorts of objects. This makes white-box testing much easier, as you can concentrate on what the code being tested sends to and receives from the mocked object, instead of worrying about faking up your own data. (Another option is not to test difficult things. Now you have no excuse.)

perl-Test-MockModule-0.05-18.fc19.noarch: Override subroutines in a module for unit testing.

perl-Test-MinimumVersion-0.101081-1.lbn19.noarch: Check whether your code requires a newer perl than you think.

perl-Test-Memory-Cycle-1.04-17.lbn19.noarch: Perl's garbage collection has one big problem: Circular references can't get cleaned up. A circular reference can be as simple as two objects that refer to each other. "Test::Memory::Cycle" is built on top of "Devel::Cycle" to give you an easy way to check for these circular references.

perl-Test-Manifest-1.23-2.lbn19.noarch: MakeMaker assumes that you want to run all of the .t files in the t/ directory in ascii-betical order during make test unless you say otherwise. This leads to some interesting naming schemes for test files to get them in the desired order. You can specify any order or any files that you like, though, with the test directive to WriteMakefile. Test::Manifest looks in the t/test_manifest file to find out which tests you want to run and the order in which you want to run them. It constructs the right value for MakeMaker to do the right thing.

perl-Test-LeakTrace-0.14-5.fc19.x86_64: Test::LeakTrace provides several functions that trace memory leaks. This module scans arenas, the memory allocation system, so it can detect any leaked SVs in given blocks. Leaked SVs are SVs that are not released after the end of the scope they have been created. These SVs include global variables and internal caches. For example, if you call a method in a tracing block, perl might prepare a cache for the method. Thus, to trace true leaks, no_leaks_ok() and leaks_cmp_ok() executes a block more than once.


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.