thanks. you've got a good point there. if the test can't load the script that I want to run tests against, I want it to crash and just doing
require 'foo';
will do that.
but I prefer using the ok() or require_ok() with a die or croak (which I didn't include in my example) because then in a test suite I get better diagnostic:
not ok 2 - require foo;
# at /source/t/foo.t line 30.
# Tried to require 'foo'.
# Error: Can't locate foo.pm in @INC (@INC contains: /source/bin
+... at (eval 17) line 2.
Died at /source/t/foo.t line 30.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.