Now that I've returned to a "normal" development environment, I've found that I miss many of the tools that were available in my previous place of employment. Three of the most useful are represented by the following vim mappings.
,t :!prove -lv %<CR>
,T :!prove -lv % \| less<CR>
,d :!perl -d -Ilib/ %<CR>
I think, perhaps, I should start a project to build custom vim tools to make standard Perl testing easier. I miss many of the things I had, but we had a vary standardized development environment. Right now, my tools work only because I ensure that I fire up vim from the proper directory. That's an awful limitation.
I particularly miss the tool that allowed us to be dumped directly into the debugger at a given test. Maybe Test::Harness should offer support for this which prove can exploit? (Though I'm not sure if Test::Harness is the best place for this.)