To further ensure that your module works in still broader environments, it would be nice to test that it works fine in "persistent" environments, such as mod_perl (e.g. a module that uses an INIT block will not be mod_perl-safe). I don't know of an easy way to test that a module is "persistent-environment-safe".

According to perlmod, CHECK and INIT blocks are not executed in a string eval. So something like this should work:

use Test::More 'no_plan';

eval "require My::Module; My::Module->import()";

# test behaviors without INIT/CHECK
[download]

Of course, you'd have to duplicate your test files to be sure of all behavior, but I'd probably tackle that by putting all the tests into helper libraries and then the duplication isn't quite so painful.

# t/Test/BehaviorA.pm
package t::Test::BehaviorA;

use base 'Exporter';
use vars qw(@EXPORT);
@EXPORT = qw( run_tests_for_A );

use Test::More tests => 42;

sub run_tests_for_A {
    # put 42 tests for Behavior A here
}
1; # need this
[download]

# 01-test-A-normal.t
use t::Test::BehaviorA qw( run_tests_for_A );

use My::Module;

run_tests_for_A();
[download]

# 01-test-A-persistant.t
use t::Test::BehaviorA qw( run_tests_for_A );

eval "require My::Module; My::Module->import()";

run_tests_for_A();
[download]

This kind of thing starts to beg for using something like Test::Class, perhaps.