view release on metacpan or  search on metacpan

README  view on Meta::CPAN

      * Test::ModuleReady

      This looks like a nice module, but what it does is already covered by
      the numerous tests in this dist...

      * Test::PerlTidy

      Br0ken install at this time... ( PerlCritic can do that! Need to
      investigate more... ) Also, all it does is... run your module through
      perltidy and compare the outputs. Not that useful imo because I never
      could get perltidy to match my prefs :(

      * Test::Install::METArequires

      This looks like a lazy way to do auto_install and potentially
      dangerous! Better to just use the prereq logic in
      Build.PL/Makefile.PL

      * Test::Perl::Metrics::Simple

      This just tests your Cyclomatic complexity and was the starting point

lib/Test/Apocalypse.pm  view on Meta::CPAN

__END__

=pod

=encoding UTF-8

=for :stopwords Apocalypse Niebur Ryan cpan testmatrix url annocpan anno bugtracker rt
cpants kwalitee diff irc mailto metadata placeholders metacpan apocal CPAN
AUTHORs al backend debian distro distros dists env hackish plugins
testsuite yml pm yay unicode blog precompiled =for stopwords ap cyclomatic
cal dist homebrew imo internet perltidy prefs prereq testrun

=head1 NAME

Test::Apocalypse - Apocalypse's favorite tests bundled into a simple interface

=head1 VERSION

  This document describes v1.006 of Test::Apocalypse - released October 25, 2014 as part of Test-Apocalypse.

=head1 SYNOPSIS

lib/Test/Apocalypse.pm  view on Meta::CPAN

This is very similar to L<Test::UseAllModules> but looks more complicated. Also, I already have enough tests that do that ;)

=item * L<Test::ModuleReady>

This looks like a nice module, but what it does is already covered by the numerous tests in this dist...

=item * L<Test::PerlTidy>

Br0ken install at this time... ( PerlCritic can do that! Need to investigate more... ) Also, all it does is... run your module
through perltidy and compare the outputs. Not that useful imo because I never could get perltidy to match my prefs :(

=item * L<Test::Install::METArequires>

This looks like a lazy way to do auto_install and potentially dangerous! Better to just use the prereq logic in Build.PL/Makefile.PL

=item * L<Test::Perl::Metrics::Simple>

This just tests your Cyclomatic complexity and was the starting point for my homebrew solution.

=back