As jbert said, tests are in ./t and have the .t extension because they are infact a suite of regression tests that test new features and check for the introduction of new bugs.

Of the modules that I play around with, I go a step further and have an actual ./tinderbox directory. These scripts are for my own use, and are .pls. I also use lib '../lib';, so that I can test during development with out have to make test

The purpose of these files is to test for new/old bugs, /and/ to stress the application. For example, my tinderbox tests take days to run versus under 30 seconds for what is in ./t. My *.t tests, however, are subsets of these tinderbox tests, and excercise parts of the code and functionality that I have deemed important.

You can never test too much, and I for one am greatful that there is a convention, and I am more than happy to follow it.

Regarding AS Perl, as far as I know perl -MCPAN -e shell still works under it. I suggest you build (and test) your module(s) using the CPAN convention. I can't imagine that it is too difficult to repackages for ppm, and I find it even more unlikely that there is no facilitiy for automated testing....of course, I could be wrong.

update: blazar properly pointed out that I meant use base when all I wanted was use lib.