Hi Jason,
On Sun, 25 Dec 2016, Jason Pyeron wrote:
Coverage works great as part on continuous integration, until a new file is
added and the unit tests are blissfully ignorant of the new file's existence.
Maybe this is not what you're looking for, but it works well
for me loading any module in t/00.load.t:
use Test::More;
# unorthodox but works fine
use Module::Pluggable search_path => ['Module::Namespace'];
my @plugins = main->plugins;
for my $module (@plugins) {
use_ok( $module );
}
done_testing;
This way I never have to touch that test again and still every new module
will show up in coverage.
Using Dist::Zilla, you can also use the Test::Compile plugin.
Of course, this only works for .pm files.
cheers,
tina
