Re^4: Should Test::Most import strict and warnings?

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;
[download]

Comment on Re^4: Should Test::Most import strict and warnings? Download Code

Replies are listed 'Best First'.
Re^5: Should Test::Most import strict and warnings? by JavaFan (Canon) on Feb 05, 2010 at 22:44 UTC
It's not that I think the person typing in `use Test::Most` will be surprised. It's the person inheriting the code.	[reply]
Re^6: Should Test::Most import strict and warnings? by chromatic (Archbishop) on Feb 06, 2010 at 18:04 UTC
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?	[reply] [d/l]