> Cons of adding -w to test runs:
> - you get warnings from dependencies (and their dependencies) because -w
> enables global action at a distance
> - using fatal warnings may cause your test suite to fail because of
> warnings in dependencies you don't directly control
- you c
* Leon Timmermans [2013-09-18T19:21:44]
> Or both just setting $Test::Harness::switches = ''…
Yes. I was cleaning out ~/tmp on the flight over here and I found this dzil
plugin:
package inc::STFUEUMM;
use Moose;
extends 'Dist::Zilla::Plugin::MakeMaker';
use namespace::autoclean;
afte
On Thu, Sep 19, 2013 at 1:17 AM, Ricardo Signes wrote:
> It looks like Module::Build already has use_tap_harness. So what's
> suggested
> is a patch to ExtUtils::MM_Any to switch from Test::Harness to
> TAP::Harness...?
>
Or both just setting $Test::Harness::switches = ''…
Leon
* Ovid [2013-09-18T04:19:28]
> As I said in my previous email on July 7th: backwards-incompatible changes to
> the backwards-compatibility layer (Test::Harness) are not a good idea. The
> proper response is to have people impacted by this issue switch to
> TAP::Harness, as was suggested several ye
As I said in my previous email on July 7th: backwards-incompatible changes to
the backwards-compatibility layer (Test::Harness) are not a good idea. The
proper response is to have people impacted by this issue switch to
TAP::Harness, as was suggested several years ago when Test::Harness 3.0 was
