http://www.perlmonks.org?node_id=821571


in reply to Re^2: Should Test::Most import strict and warnings?
in thread Should Test::Most import strict and warnings?

Test::Most, not Test::More. That's a very important difference here.
Sorry, I'm just used to typing Test::More.

But that doesn't change my arguments. I wouldn't want any module to turn on a pragma in the calling scope - unless that is its specific purpose. turn::on::all::pragmata should turn it on. But not something from the Test::* namespace.

Replies are listed 'Best First'.
Re^4: Should Test::Most import strict and warnings?
by zwon (Abbot) on Feb 05, 2010 at 18:47 UTC

    I'd say that reducing boilerplate code is one of the main advantages of Test::Most, so I think it will be logically if it will enable strict and warnings. The people who don't love surprises and magic can always replace it with:

    use strict; use warnings; use Test::More; use Test::Exception; use Test::Differences; use Test::Deep; use Test::Warn;
      It's not that I think the person typing in use Test::Most will be surprised.

      It's the person inheriting the code.

        If the person inheriting the code cannot type perldoc Test::Most to find out "what that funny-looking line at the top of this PERL SCRIPT does", what chance does he or she have of doing anything useful with the program?