Re: Add optional modules to TEST

So, I confirm the EXTENDED_TESTING works with cpancover, but you do need AUTOMATED_TESTING for cpantesters, as they don't install "recommends" options, so I went with something like:

my $extra_test =
  ( $ENV{EXTENDED_TESTING} || $ENV{AUTOMATED_TESTING} )
  ? 'requires'
  : 'recommends';

$WriteMakefileArgs{META_MERGE}->{prereqs}->{test} = {
    $extra_test => {
        'Test2::Plugin::BailOnFail' => '0',
        'Sub::Override'             => '0'
    }
};
[download]

Comment on Re: Add optional modules to TEST_REQUIRES? Download Code

Replies are listed 'Best First'.
Re^2: Add optional modules to TEST_REQUIRES? by haukex (Archbishop) on Nov 25, 2019 at 21:10 UTC
`Test2::Plugin::BailOnFail`, `Sub::Override` I know this goes against the grain of this thread, and I'm glad you got it working, but: Test2::Plugin::BailOnFail is basically just five lines of code, and Sub::Override is a more sophisticated version of `local *subname = sub { print "overridden" };`. As I said, personally, in a case like this I wouldn't depend on those modules at all.	[reply] [d/l] [select]