If this is all part of one module, then you probably have something like:

MANIFEST
README
Makefile.PL
lib/Foo/Bar.pm
lib/Foo/Bar/Baz.pm
lib/Blah/Bleh.pm

[download]

If so, just add a t/ subdirectory at the top-level and create your tests there:

t/foo-bar.t
t/foo-bar-baz.t
t/blah-bleh.t

[download]

As long as you're using ExtUtils::MakeMaker to create your Makefile, the normal test process (perl Makefile.PL; make; make test) will then run all your tests.

Note that with tests you might not wind up creating one test file per module, but rather testing areas of functionality which may use several modules at once. The test names I picked above were just an example.

Chris
M-x auto-bs-mode

In reply to Re: Testing: where does the t directory go? by lachoy
in thread Testing: where does the t directory go? by jplindstrom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.