Work around JSON::Any not being future-proof

https://rt.cpan.org/Ticket/Display.html?id=89853 perigrin/json-any#2
Perl5 · Oct 31, 2013 · de895f0 · de895f0
1 parent bcb37ec
commit de895f0
Showing 1 changed file with 3 additions and 4 deletions.
diff --git a/t/admin/10script.t b/t/admin/10script.t
@@ -18,11 +18,10 @@ BEGIN {
   delete $ENV{JSON_ANY_ORDER};
 }
 
-use JSON::Any;
-
 $ENV{PATH} = '';
 $ENV{PERL5LIB} = join ($Config{path_sep}, @INC);
 
+require JSON::Any;
 my @json_backends = qw/XS JSON DWIW/;
 
 # test the script is setting @INC properly
@@ -42,9 +41,9 @@ cmp_ok ($? >> 8, '==', 71, 'Correct schema loaded via testconfig');
 
 for my $js (@json_backends) {
 
-    eval {JSON::Any->import ($js) };
     SKIP: {
-        skip ("JSON backend $js is not available, skip testing", 1) if $@;
+        eval {JSON::Any->import ($js); 1 }
+          or skip ("JSON backend $js is not available, skip testing", 1);
 
         local $ENV{JSON_ANY_ORDER} = $js;
         eval { test_dbicadmin () };