Right before releasing I use  perl -e "$ENV{RELEASE_TESTING}=1; system $^X, 'Makefile.PL'; system 'dmake disttest'; " because dmake is my  perl -V:make and my shell is cmd.exe, so I can't RELEASE_TESTING=1 make disttest ;)

Before that I use  prove -Ilib t\03specific.t or  dmake test or  prove -vb t\04specifi.t depending if i'm starting from scratch, fixing a specific bug, writing a new test, verifying a bug, or whatever ... type once then up-arrow+enter to repeat from my commandline history

Pretty much regular stuff. I don't like the editor integration(F5/Ctrl+F7/whatever) or file watchers(run test on save, autoprove)

See also

• Starting a module with Module::Starter
• How to make a CPAN Module Distribution
• José's Guide for creating Perl modules
• RFC: How to Release Modules on CPAN in 2011
• Do Pure Perl CPAN packages really need to use ExtUtils::Command::MM?
• Why I hate Dist::Zilla
• What are all the possible ways to deploy Perl code on multiple servers?