Re: TAP::Harness and -w
[email protected] (Leon Timmermans) Sun, 7 Jul 2013 19:26:25 +0200
| Newsgroups | perl.qa |
|---|---|
| Message-ID | <CAHhgV8hpBWzz8EVQNEA6LjrOX6iFwAdp7PoUTsoBFPi9mV1AaQ@mail.gmail.com> |
On Sun, Jul 7, 2013 at 6:00 PM, Ovid <[email protected]> wrote: > What toolchain software is being impacted by this and how hard would it be to make the switch? AFAIK only ExtUtils::MakeMaker and Module::Build use it. The latter can already use TAP::Harness, but there are some details we'd might want to fix first (such as environmental variables). Module::Build::Tiny is already using TAP::Harness exclusively. > People have long known that TAP::Harness is a better alternative to Test::Harness, but the compatibility layer meant that people wouldn't have to make that switch right away. Given toolchain still has to support perl < 5.10.1, using TAP::Harness means an extra non-core dependency. I suspect that's the real reason. Possibly we could use TAP::Harness but fall back on Test::Harness if the former is not present. Disadvantage may be different test results depending on this because of the -w issue. Leon