Re: cpan mod test probs

First of all, the mem prerequisite. In your last couple of releases it's correctly listed as a dependency, so you've done your job. No need to check for its presence in your tests. If a CPAN client tries to run your tests without installing it, then it's its own damn fault that they fail.

Unsetting $ENV{PERL5OPT} in your script will achieve very little. By the time your script starts running, the effects of the environment variable have already happened. Instead try to get your test script and module to behave correctly when Unicode features have been enabled.

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

Comment on Re: cpan mod test probs Download Code

Replies are listed 'Best First'.
Re^2: cpan mod test probs by perl-diddler (Chaplain) on Nov 08, 2013 at 08:45 UTC
No need to check for its presence in your tests. If a CPAN client tries to run your tests without installing it, then it's its own damn fault that they fail True, but I want to make sure they know the reason and how they can fix it. At least with explicit tests for the dep, I can fail and early-exit the tests so they know nothing ran and can see a message about 'why'...	[reply]
Re^3: cpan mod test probs by Corion (Patriarch) on Nov 08, 2013 at 09:14 UTC
See Test::More about testing, especially the section on BAIL OUT. This is especially for when your test run detects a situation where further testing is impossible.	[reply]
Re^4: cpan mod test probs by perl-diddler (Chaplain) on Nov 08, 2013 at 10:08 UTC
That's what I used. If the prereqs aren't there, I figured, the tests aren't going to run. ;-)	[reply]