in reply to Re^2: Running tests on modules generated by Module::Starter still in /lib directory
in thread Running tests on modules generated by Module::Starter still in /lib directory

Hi nysus,

Did you try what choroba suggested? The way I run my tests for all my (pure-Perl) modules is prove -l from the command line from the base directory of the module. make should not be necessary unless you've got XS code that you need to compile, but even then, prove should be able to run all the tests (AFAIK you need prove -lb in that case).

Hope this helps,
-- Hauke D

Replies are listed 'Best First'.
Re^4: Running tests on modules generated by Module::Starter still in /lib directory
by nysus (Parson) on Feb 12, 2017 at 18:54 UTC

    I'm attempting to automate the process and run the tests from VIM with a shortcut command. See my comment further down for details.

    $PM = "Perl Monk's";
    $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate";
    $nysus = $PM . ' ' . $MCF;
    Click here if you love Perl Monks

      I don't do vim. Can it cd in shortcuts?

      ($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord }map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

        I figured it out. I made a simple hack to the perltests script that added ./lib<code> to the <code>Tap::Harness object's @INC.

        Thanks for your help working me through this.

        $PM = "Perl Monk's";
        $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon Curate";
        $nysus = $PM . ' ' . $MCF;
        Click here if you love Perl Monks