We use Test::More all the time.

Every <module>.t we write has a corresponding t/<module>.t test file written for it.

I've included a real Makefile.PL from one of our projects, and a sample Test::More template .t file.

You should also read the ExtUtils::MakeMaker doco for more sophisticated ways of calling make test

# Makefile.PL
use ExtUtils::MakeMaker;

WriteMakefile(
              NAME         => 'txu_bims',
              VERSION_FROM => 'VERSION.pm',
              test         => {TESTS => './TXU/BIMS/t/*.t ./TXU/t/*.t'
+}, # how to pass multiple test paths
              PMLIBDIRS    => ['./TXU/BIMS', './TXU'],
              PREREQ_PM    => {
                               Log::Log4perl => 0.36,
                              },
             );
[download]

# template Module/Under/t/Test.t
#!/usr/bin/perl -w

use strict;

use Test::More qw(no_plan);

use Module::Under::Test;

# test go here
my $obj = Module::Under::Test->new();
isa_ok($obj, 'Module::Under::Test');

is($obj->method(), 'expected output', 'standard test');

is_deeply($obj->meth_retn_ref(), {complex => {structure => ['here']}},
+ 'method returns ref to complex structure');
[download]

After this, its as simple as ...

perl Makefile.PL
make test
[download]

More complex examples of calling make test are ...

• make test TEST_VERBOSE=1
  for more detailed information on test execution
• make testdb TEST_FILE=path/to/script.t TESTDB_SW=-d:ptkdb
  to run just path/to/script.t under the GUI debugger ptkdb (which is a great debugger

*UPDATE* - proxy dropped out half way through uploading this - added the point list