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.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by jplindstrom (594) on 2005.07.14 12:28 (#41929) Journal
    I usually just run prove from within the t directory and put a
    use lib "../lib";
    in each test file.
    • prove respects the -I command-line option (and you can stack them the same way you can with perl itself):

      prove -I/some/project/lib -I../lib

      It also looks for a PROVE_SWITCHES environment variable, which I usually load up with something like this:

      -I/some/shared/lib -I/my/project/lib

      This way, I don't have to modify the test scripts at all, and if I use absolute paths, I can run the tests from whatever directory I happen to be in at the time.