Stop forcefully loading Test::Leaner for the threads feature

Test::Leaner is more reliable than Test::More, but we need it here only for
a diagnostic when tests are forced. As long as we don't plan, this should
have no influence on the rest of the test, so let the user decide which
module to use.

diff --git a/lib/VPIT/TestHelpers.pm b/lib/VPIT/TestHelpers.pm
index 01aff874a8f7a8563554437cf3aee322870b405a..bae97851cc47e8a8ac86eed95cc9e77f56db42d0 100644 (file)
--- a/lib/VPIT/TestHelpers.pm
+++ b/lib/VPIT/TestHelpers.pm
@@ -568,10 +568,6 @@ L<threads> 1.67
 
 L<threads::shared> 1.14
 
-=item -
-
-L<Test::Leaner>
-
 =back
 
 =item *
@@ -633,8 +629,6 @@ sub init_threads {
  load_or_skip_all 'threads',         $force ? '0' : '1.67', [ ];
  load_or_skip_all 'threads::shared', $force ? '0' : '1.14', [ ];
 
- require Test::Leaner;
-
  diag "Threads testing forced by \$ENV{$force_var}" if $force;
 
  return spawn => \&spawn;