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.

Test::Verbose 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • make test (Score:1)

    by jplindstrom (594) on 2005.01.12 10:43 (#37403) Journal
    It does require a makefile, no?

    I don't have that for my applications. A typical directory structure looks like this:
    /project
      /bin
      /lib
        /My
          Module.pm
        /The
          /Other
             Mod.pm
      /t
        My-Module.t
        The-Other-Mod.t
    The .t files contain a 'use lib "lib", "../lib";' to point to the module directory.

    Like chromatic I usually just type perl t/FILENAME to run a certain test file, but I also enter the t directory and run prove to test them all.

    If I have a huge amount of modules in my lib dir, what kind of makefile setup would I have? One for each? One for them all? Where would it go?
    • You would have one Makefile.PL with a very simple contents:
      use ExtUtils::MakeMaker;
      WriteMakefile(
          NAME => 'projectname',
          AUTHOR => 'me',
          VERSION => '1.0',
          ABSTRACT => 'this is my project',
      );
      You can change a few of those to extract better info, but you don't really need it.

      ExtUtils::MakeMaker will find all your .pm files under a lib/ directory.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.