in reply to Setting up a test suite in perl

Why write separate test files if you're going to run them together? Alternately posed, why mash test files together under one runner if you've already separated them?

In place of segments, I'd use subdirectories under t/. Then you can use prove to run individual segments. (If you're using Module::Build or even ExtUtils::MakeMaker, you can add your own ./Build or make target to run the tests for individual segments.

Your make test (or ./Build test) should run all tests under t/ effectively, though (I forget if) you may have to specify recursive traversal of t/.

Replies are listed 'Best First'.
Re^2: Setting up a test suite in perl
by jasoncollins (Novice) on Nov 10, 2009 at 04:44 UTC

    I do like the idea of breaking down the test into individual directories, this way I can store all the data related with the test, input or output, in that directory and I can run all the tests using:

    make TEST_FILES=t/*/*.t TEST_VERBOSE=1 test

    Thanks for your help!