Totally agree with chromatic. Keep the tests in the same directories as the modules -- makes it easier to keep them up-to-date. While File::Find is a good wrapper for a programmatic smoke suite, the "prove" command (from T::Harness? Or is it from T::More? I forget) is great for running the suite from the command line, often, and flexibly.

More testing = less bugs = less work = more happiness

water


In reply to Re: Organizing Module Tests Sensibly by water
in thread Organizing Module Tests Sensibly by skyknight

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