Test-DBIx-Class 0.34
Kwalitee Issues
- 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: Test::DBIx::Class::Example::Schema, Test::DBIx::Class::Example::Schema::DefaultRS, Test::DBIx::Class::Example::Schema::Result, Test::DBIx::Class::Example::Schema::Result::CD, Test::DBIx::Class::Example::Schema::Result::CD::Artist, Test::DBIx::Class::Example::Schema::Result::CD::Track, Test::DBIx::Class::Example::Schema::Result::Company, Test::DBIx::Class::Example::Schema::Result::Company::Employee, Test::DBIx::Class::Example::Schema::Result::Job, Test::DBIx::Class::Example::Schema::Result::Person, Test::DBIx::Class::Example::Schema::Result::Person::Artist, Test::DBIx::Class::Example::Schema::Result::Person::Employee, Test::DBIx::Class::Example::Schema::Result::Phone
- no_pod_errors
-
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: Test-DBIx-Class-0.34/lib/Test/DBIx/Class.pm -- Around line 1360: You forgot a '=back' before '=head1'
- 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: maint/Maker.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::DBIx::Class::Example::Schema, Test::DBIx::Class::Example::Schema::DefaultRS, Test::DBIx::Class::Example::Schema::Result, Test::DBIx::Class::Example::Schema::Result::CD, Test::DBIx::Class::Example::Schema::Result::CD::Artist, Test::DBIx::Class::Example::Schema::Result::CD::Track, Test::DBIx::Class::Example::Schema::Result::Company, Test::DBIx::Class::Example::Schema::Result::Company::Employee, Test::DBIx::Class::Example::Schema::Result::Job, Test::DBIx::Class::Example::Schema::Result::Person, Test::DBIx::Class::Example::Schema::Result::Person::Artist, Test::DBIx::Class::Example::Schema::Result::Person::Employee, Test::DBIx::Class::Example::Schema::Result::Phone
- 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.
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Modules
Name | Abstract | Version | View |
---|---|---|---|
Test::DBIx::Class | Easier test cases for your DBIx::Class applications | 0.34 | metacpan |
Test::DBIx::Class::Example::Schema | A basic schema you can use for testing | metacpan | |
Test::DBIx::Class::Example::Schema::DefaultRS | The default ResultSet | metacpan | |
Test::DBIx::Class::Example::Schema::Result | The base result class | metacpan | |
Test::DBIx::Class::Example::Schema::Result::CD | A cd | metacpan | |
Test::DBIx::Class::Example::Schema::Result::CD::Artist | Artist Role | metacpan | |
Test::DBIx::Class::Example::Schema::Result::CD::Track | Tracks on a CD | metacpan | |
Test::DBIx::Class::Example::Schema::Result::Company | A company | metacpan | |
Test::DBIx::Class::Example::Schema::Result::Company::Employee | Company To Employee M2M | metacpan | |
Test::DBIx::Class::Example::Schema::Result::Job | A Job | metacpan | |
Test::DBIx::Class::Example::Schema::Result::Person | The base result class | metacpan | |
Test::DBIx::Class::Example::Schema::Result::Person::Artist | Artist Role | metacpan | |
Test::DBIx::Class::Example::Schema::Result::Person::Employee | Employee Role | metacpan | |
Test::DBIx::Class::Example::Schema::Result::Phone | The base result class | metacpan | |
Test::DBIx::Class::Example::Schema::ResultSet | A base ResultSet Class | metacpan | |
Test::DBIx::Class::FixtureCommand::Populate | Install fixtures using Populate | metacpan | |
Test::DBIx::Class::FixtureCommand::PopulateMore | Install fixtures using PopulateMore | metacpan | |
Test::DBIx::Class::Role::FixtureCommand | Role that a FixtureCommand must consume | metacpan | |
Test::DBIx::Class::SchemaManager | Manages a DBIx::Class::SchemaManager for Testing | metacpan | |
Test::DBIx::Class::SchemaManager::Trait::SQLite | The Default Role | metacpan | |
Test::DBIx::Class::SchemaManager::Trait::Testmysqld | deploy to a test mysql instance | metacpan | |
Test::DBIx::Class::SchemaManager::Trait::Testpostgresql | deploy to a test Postgresql instance | metacpan | |
Test::DBIx::Class::Types | Type Constraint Library | metacpan |