Skip Menu |

This queue is for tickets about the strictures CPAN distribution.

Report information
The Basics
Id: 78252
Status: resolved
Priority: 0/
Queue: strictures

People
Owner: Nobody in particular
Requestors: DOY [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 1.003001
Fixed in: (no value)



Subject: unnecessary warnings during tests
I'm testing a module which uses DBIx::Class, which uses SQL::Abstract, which uses Moo, which uses strictures. I'm getting warnings like strictures.pm extra testing active but couldn't load all modules. Missing were: indirect multidimensional bareword::filehandles Extra testing is auto-enabled in checkouts only, so if you're the author of a strictures using module you need to run: cpan indirect multidimensional bareword::filehandles but these modules are not required by your users. which is completely unnecessary, because these modules aren't going to catch any issues in my code - they all check syntax during compilation, and work lexically. I can see how this would be useful while running Moo's test suite, but I can't really see how it's helpful to me. Can this "extra testing" be disabled unless you're actually testing a module that uses strictures? It's pretty irritating.
On Fri Jul 06 14:29:02 2012, DOY wrote: Show quoted text
> I'm testing a module which uses DBIx::Class, which uses SQL::Abstract,
Oops, that should be SQL::Translator. But the point still stands. -doy
Subject: Re: [rt.cpan.org #78252] unnecessary warnings during tests
Date: Fri, 6 Jul 2012 21:59:49 -0400
To: "bug-strictures [...] rt.cpan.org" <bug-strictures [...] rt.cpan.org>
From: John Napiorkowski <jjn1056 [...] yahoo.com>
I did a branch in the repo repo that has a solution to this take a look it is probably not exactly right but maybe a step Sent from my iPhone On Jul 6, 2012, at 2:29 PM, "Jesse Luehrs via RT" <bug-strictures@rt.cpan.org> wrote: Show quoted text
> Fri Jul 06 14:29:02 2012: Request 78252 was acted upon. > Transaction: Ticket created by DOY > Queue: strictures > Subject: unnecessary warnings during tests > Broken in: 1.003001 > Severity: (no value) > Owner: Nobody > Requestors: DOY@cpan.org > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=78252 > > > > I'm testing a module which uses DBIx::Class, which uses SQL::Abstract, > which uses Moo, which uses strictures. I'm getting warnings like > > strictures.pm extra testing active but couldn't load all modules. > Missing were: > > indirect multidimensional bareword::filehandles > > Extra testing is auto-enabled in checkouts only, so if you're the author > of a strictures using module you need to run: > > cpan indirect multidimensional bareword::filehandles > > but these modules are not required by your users. > > which is completely unnecessary, because these modules aren't going to > catch any issues in my code - they all check syntax during compilation, > and work lexically. I can see how this would be useful while running > Moo's test suite, but I can't really see how it's helpful to me. Can > this "extra testing" be disabled unless you're actually testing a module > that uses strictures? It's pretty irritating.
On Fri Jul 06 14:29:02 2012, DOY wrote: Show quoted text
> I'm testing a module which uses DBIx::Class, which uses SQL::Abstract, > which uses Moo, which uses strictures. I'm getting warnings like > > strictures.pm extra testing active but couldn't load all modules. > Missing were:
To my knowledge, 1.4+ fixes this by only firing them when the code calling strictures is in lib/ or t/