view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

	and the t/00_compile_pm.t strategy of:

		use strict;
		use warnings;
		use Test::Compile;
		BEGIN { all_pm_files_ok(); }
	
	If we do not put it in the BEGIN block then we run into the problem
	of the INIT {} block for the Test::Class that runs too late, eg:
	
	t/00_compile_pm.t ............. 1/2 Too late to run INIT block at 

 view release on metacpan or  search on metacpan

lib/Wetware/Test/Class.pm  view on Meta::CPAN

 
 use strict;
 use warnings;
 use Test::Compile;

 all_pm_files_ok();

=back

I have not yet solved a way to avoid this conflict.

 view release on metacpan or  search on metacpan

t/00-compile-pm.t  view on Meta::CPAN

use warnings;
use 5.010;
use Test::More;
use Test::Compile;

all_pm_files_ok();

 view release on metacpan or  search on metacpan

inc/Module/Install/PRIVATE/Fix_Standard_Tests.pm  view on Meta::CPAN

  # Update compile test
  {
    my $test = read_text('t/000_standard__compile.t', undef, 1);

    $test =~ s#all_pm_files_ok\(\)#all_pl_files_ok('blib/script/$script_name')# or die "Couldn't update compile test";

    write_text('t/000_standard__compile.t', $test, undef, 1);
  }

  # Update critic test

 view release on metacpan or  search on metacpan

t/00_compile.t  view on Meta::CPAN

eval "use Test::Compile 0.08";
plan skip_all => "Test::Compile 0.08 required for testing compilation"
    if $@;

my @pmdirs = qw(lib blib sbin bin);
all_pm_files_ok(all_pm_files(@pmdirs));

 view release on metacpan or  search on metacpan

inc/Module/Install/StandardTests.pm  view on Meta::CPAN

        BEGIN {
            use Test::More;
            eval "use Test::Compile";
            Test::More->builder->BAIL_OUT(
                "Test::Compile required for testing compilation") if $@;
            all_pm_files_ok();
        }
    /);
}