Kwalitee Issues

has_license_in_source_file

Add =head1 LICENSE and the text of the license to the main module in your code.

prereq_matches_use

List all used modules in META.yml requires

Error:

  • Config
  • English
  • IO::Handle
  • MIME::Base64
  • POSIX
  • Storable
  • constant
  • strict
  • vars

has_known_license_in_source_file

Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.

has_meta_json

Add a META.json to the distribution. Your buildtool should be able to autogenerate it.

meta_yml_declares_perl_version

If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.

proper_libs

Move your *.pm files in a directory named 'lib'. The directory structure should look like 'lib/Your/Module.pm' for a module named 'Your::Module'. If you need to provide additional files, e.g. for testing, that should not be considered for Kwalitee, then you should look at the 'provides' map in META.yml to limit the files scanned; or use the 'no_index' map to exclude parts of the distribution.

Error: Suites/Customer.pm, Suites/CustomerTest.pm, Suites/CustomerTest1.pm, Suites/CustomerTest2.pm, Suites/TS_SubSuite1.pm, Suites/TS_SubSuite2.pm, Suites/TS_SubSuite3.pm, Suites/TS_TopLevel.pm

use_warnings

Add 'use warnings' (or its equivalents) to all modules (this will require perl > 5.6), or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.

Error: Suites::Customer, Suites::CustomerTest, Suites::CustomerTest1, Suites::CustomerTest2, Suites::TS_SubSuite1, Suites::TS_SubSuite2, Suites::TS_SubSuite3, Suites::TS_TopLevel, Test::Unit::GTestRunner, Test::Unit::GTestRunner::Lister, Test::Unit::GTestRunner::Worker

meta_yml_has_provides

Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.

meta_yml_has_repository_resource

Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).

Modules

Name Abstract Version View
Suites::Customer metacpan
Suites::CustomerTest metacpan
Suites::CustomerTest1 metacpan
Suites::CustomerTest2 metacpan
Suites::TS_SubSuite1 metacpan
Suites::TS_SubSuite2 metacpan
Suites::TS_SubSuite3 metacpan
Suites::TS_TopLevel metacpan
Test::Unit::GTestRunner Unit testing framework helper class 0.04 metacpan
Test::Unit::GTestRunner::Lister Load and list test suites metacpan
Test::Unit::GTestRunner::Worker Worker class for GTestRunner metacpan

Provides

Name File View
GTestRunnerSuite lib/Test/Unit/GTestRunner/Worker.pm metacpan
Test::Unit::GTestRunner::Node lib/Test/Unit/GTestRunner.pm metacpan
Test::Unit::GTestRunner::TiedHandle lib/Test/Unit/GTestRunner/Worker.pm metacpan

Other Files

Build.PL metacpan
ChangeLog metacpan
MANIFEST metacpan
META.yml metacpan
Makefile.PL metacpan
README metacpan
README-NLS metacpan
README-TRANSLATIONS metacpan