Test-WWW-Selenium 1.19
Kwalitee Issues
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Test-WWW-Selenium-1.19/lib/WWW/Selenium.pm -- Around line 2862: Expected text after =item, not a bullet Around line 2886: Expected text after =item, not a bullet Around line 2907: Expected text after =item, not a bullet Around line 2937: Expected text after =item, not a bullet Around line 2958: Expected text after =item, not a bullet Test-WWW-Selenium-1.19/util/WWW/Selenium/XMLParseUtils.pm -- Around line 117: '=item' outside of any '=over' =over without closing =back Test-WWW-Selenium-1.19/util/create_www_selenium.pl -- Around line 139: =cut found outside a pod block. Skipping to next block. Around line 417: Expected text after =item, not a bullet Around line 441: Expected text after =item, not a bullet Around line 462: Expected text after =item, not a bullet Around line 492: Expected text after =item, not a bullet Around line 513: Expected text after =item, not a bullet
- 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.
- has_meta_json
-
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
- 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: util/WWW/Selenium/XMLParseUtils.pm
- 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: Test::WWW::Selenium
- consistent_version
-
Split the distribution, or fix the version numbers to make them consistent (use the highest version number to avoid version downgrade).
Error: 0.93,1.19
- 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.
- has_security_doc
-
Add SECURITY(.pod|md). See Software::Security::Policy.
- security_doc_contains_contact
-
Add SECURITY(.pod|md) and add a contact address. See Software::Security::Policy.
- has_contributing_doc
-
Add CONTRIBUTING(.pod|md). See https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.
Modules
| Name | Abstract | Version | View |
|---|---|---|---|
| Test::WWW::Selenium | Test applications using Selenium Remote Control | 1.19 | metacpan |
| WWW::Selenium | Perl Client for the Selenium Remote Control test tool | 0.93 | metacpan |
| WWW::Selenium::Util | Utility code to help test using Selenium | metacpan | |
| WWW::Selenium::XMLParseUtils | metacpan |