Re: Seeking advice for portable test suite

What happens when you give an explicit plan? tests => 1 that is?

The standard installations of Perl modules doesn't provide a good way for latter uninstall. But in your case you could put a fake Test::Perl::Critic in your PERL5LIB that intentionally fails to load.

Comment on Re: Seeking advice for portable test suite Download Code

Replies are listed 'Best First'.
Re^2: Seeking advice for portable test suite by f00li5h (Chaplain) on Jan 13, 2007 at 10:09 UTC
You could perhpas bundle the `Test::` modules with your code as you roll it out too... Although I'll be told instantly why this is a bad idea... (i'm thinking size, risk of freezing the module at a fixed version, extra administration etc) `@_=qw; ask f00li5h to appear and remain for a moment of pretend better than a lifetime;;s;;@_[map hex,split'',B204316D8C2A4516DE];;y/05/os/&print;`	[reply] [d/l] [select]
Re^2: Seeking advice for portable test suite by hesco (Deacon) on Jan 13, 2007 at 09:28 UTC
Thanks, that sounds like a great idea, to load a broken T::P::C in my test environment, that is. I'll have to try that. Result on Test::Perl::Critic enabled machine, with "tests => 1". `1..1 You tried to plan twice at t/perlcritic.t line 9. # Looks like your test died before it could output anything.` [download] if( $lal && $lol ) { $life++; }	[reply] [d/l]