Skip to content

Commit

Permalink
Add warnings and strict pragmas to tests
Browse files Browse the repository at this point in the history
In the case of `inheritance.t` warnings and strict did need to be turned on.
In the POD tests the strictures aren't strictly necessary, however including
them is best practice.
  • Loading branch information
paultcochrane committed Oct 24, 2015
1 parent 71ca6b5 commit e8020a4
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 0 deletions.
3 changes: 3 additions & 0 deletions t/inheritance.t
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
#!/usr/bin/perl

use warnings;
use strict;

use Test::MockModule;
use Test::More;

Expand Down
4 changes: 4 additions & 0 deletions t/pod.t
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
#!/usr/bin/perl
#$Id: pod.t,v 1.1.1.1 2004/11/28 23:38:28 simonflack Exp $

use warnings;
use strict;

use Test::More;
eval "use Test::Pod 1.00";
plan skip_all => "Test::Pod 1.00 required for testing POD" if $@;
Expand Down
4 changes: 4 additions & 0 deletions t/pod_coverage.t
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
#!/usr/bin/perl
#$Id: pod_coverage.t,v 1.1 2005/03/24 22:23:38 simonflack Exp $

use warnings;
use strict;

use Test::More;
eval "use Test::Pod::Coverage 1.00";
plan skip_all => "Test::Pod::Coverage 1.00 required for testing pod coverage" if $@;
Expand Down

0 comments on commit e8020a4

Please sign in to comment.