perl::critic::policy::testinganddebugging::requiretestlabels(3) [centos man page]

Perl::Critic::Policy::TestingAndDebugging::RequireTestLaUser(Contributed Perl DocumPerl::Critic::Policy::TestingAndDebugging::RequireTestLabels(3)

NAME

       Perl::Critic::Policy::TestingAndDebugging::RequireTestLabels - Tests should all have labels.

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       Most Perl modules with regression tests use Test::More as infrastructure for writing and running those tests.  It has an easy, procedural
       syntax for writing comparisons of results to expectations.

       Most of the Test::More functions allow the programmer to add an optional label that describes what each test is trying to judge.  When a
       test goes wrong, these labels are very useful for quickly determining where the problem originated.

       This policy enforces that all Test::More functions have labels where applicable.  This only applies to code that has a "use Test::More" or
       "require Test::More" declaration (see below to add more test modules to the list).

CONFIGURATION

       A list of additional modules to require label parameters be passed to their methods can be specified with the "modules" option.	The list
       must consist of whitespace-delimited, fully-qualified module names.  For example:

	   [TestingAndDebugging::RequireTestLabels]
	   modules = My::Test::SubClass  Some::Other::Module

       The module list always implicitly includes Test::More.

AUTHOR

       Chris Dolan <cdolan@cpan.org>

COPYRIGHT

       Copyright (c) 2006-2011 Chris Dolan.

       This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.16.3							    2014-06-09	   Perl::Critic::Policy::TestingAndDebugging::RequireTestLabels(3)

Perl::Critic::Policy::TestingAndDebugging::RequireUseStrUser3Contributed Perl DocuPerl::Critic::Policy::TestingAndDebugging::RequireUseStrict(3pm)

NAME

       Perl::Critic::Policy::TestingAndDebugging::RequireUseStrict - Always "use strict".

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       Using strictures is probably the single most effective way to improve the quality of your code.	This policy requires that the 'use strict'
       statement must come before any other statements except "package", "require", and other "use" statements.  Thus, all the code in the entire
       package will be affected.

       There are special exemptions for Moose, Moose::Role, and Moose::Util::TypeConstraints because they enforces strictness; e.g.  'use Moose'
       is treated as equivalent to 'use strict'.

       The maximum number of violations per document for this policy defaults to 1.

CONFIGURATION

       If you take make use of things like Moose::Exporter, you can create your own modules that import the strict pragma into the code that is
       "use"ing them.  There is an option to add to the default set of pragmata and modules in your .perlcriticrc: "equivalent_modules".

	   [TestingAndDebugging::RequireUseStrict]
	   equivalent_modules = MooseX::My::Sugar

SEE ALSO

       Perl::Critic::Policy::TestingAndDebugging::ProhibitNoStrict

AUTHOR

       Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

COPYRIGHT

       Copyright (c) 2005-2011 Imaginative Software Systems.  All rights reserved.

       This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.  The full text of this license
       can be found in the LICENSE file included with this module

perl v5.14.2							    2012-06-07	  Perl::Critic::Policy::TestingAndDebugging::RequireUseStrict(3pm)