JS-Test-Simple 0.23
- Released by
- INGY
- Version
- Release Date
- 2008-06-20
- Kwalitee
- 143.75
- Core Kwalitee
- 87.5
- LINKS
JS-Test-Simple 0.23 Deleted
Kwalitee Issues
- meta_json_conforms_to_known_spec
-
Take a look at the META.json Spec at https://metacpan.org/pod/CPAN::Meta::History::Meta_1_4 (for version 1.4) or https://metacpan.org/pod/CPAN::Meta::Spec (for version 2), and change your META.json accordingly.
Error: Key 'Test.Builder' is not a legal module name. (provides -> Test.Builder) [Validation: 1.2];Key 'Test.Harness' is not a legal module name. (provides -> Test.Harness) [Validation: 1.2];Key 'Test.Harness.Browser' is not a legal module name. (provides -> Test.Harness.Browser) [Validation: 1.2];Key 'Test.Harness.Director' is not a legal module name. (provides -> Test.Harness.Director) [Validation: 1.2];Key 'Test.More' is not a legal module name. (provides -> Test.More) [Validation: 1.2];Key 'Test.Simple' is not a legal module name. (provides -> Test.Simple) [Validation: 1.2]
- use_strict
-
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Error: JS::Test::Simple
- main_module_version_matches_dist_version
-
Make sure that the main module name and version are the same of the distribution.
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: JS-Test-Simple-0.23/doc/pod/Test/Builder.pod -- Around line 627: '=item' outside of any '=over' JS-Test-Simple-0.23/doc/pod/Test/Harness/Director.pod -- Around line 58: You forgot a '=back' before '=head1'
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: JS::Test::Simple
- 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).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.