I have a tool for that, too. It's ~/bin/newtest:

#!/usr/bin/perl -w

use strict;

use File::Path;
use File::Basename;

my $progfile = basename( $0 );
die "$progfile <modname> <test filename>\n" unless @ARGV >= 2;
my ($modname, $filename) = @ARGV;

my $filepath = dirname( $filename );

mkpath( $filepath ) unless -e $filepath;
open my $out, '>', $filename or die "Can't open '$filename': $!";

print $out <<END_HERE;
#!/usr/bin/perl -w

BEGIN
{
    chdir 't' if -d 't';
    use lib '../lib', '../blib/lib';
}

use strict;
use Test::More 'no_plan'; # tests => 1;

my \$module = '$modname';
use_ok( \$module ) or exit;
END_HERE

[download]

For Some::Module, run newtest Some::Module t/testfile.t.

In reply to Automating Writing Regression Tests by chromatic
in thread Thoughts on making modules by BrentDax

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.