Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

use_ok or die, die, die More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Why use use_ok, require_ok at all? (Score:2)

by IlyaM (2933)

I just don't use them at all as ordinary use and require cause nearly exactly same test failure if there is something wrong with module you are trying to load.

--
Ilya Martynov (http://martynov.org/ [martynov.org])
- Re: (Score:1)
  
  by Aristotle (5147)
  
  Agreed.
Another approach... (Score:1)

by Alias (5735)

I use a 01_compile.t in all my modules that contains all the load-integrity testing. So regular use_ok stuff, plugin loading, checking $VERSION values all match, does Exporter export what it is supposed to, etc...

That way I get a full report on load failures, and the rest of the tests can totally ignore the issue and load normally.
- Re: (Score:2)
  
  by Ovid (2709)
  
  That's what I've done with Test::Harness [cpan.org], but this isn't my code base.
  - Re: (Score:1)
    
    by jplindstrom (594)
    
    It's our code base, including yours, no?
    
    And I believe we already have a test file that loads all modules, but I'm not 100% certain (well, you shouldn't trust anything I say today anyway 8^)

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.