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

In reply to Re: how do you build and test your modules locally before publishing by Anonymous Monk
in thread how do you build and test your modules locally before publishing by gideondsouza

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.