in reply to Testing CLI commands on Windows machines

As a side note, you would benefit from using CI testing. You can use Travis_CI for OSX and Linux testing and AppVeyor for Windows. Automatic testing of various OS & perl versions before you release your module to cpan.

  • Comment on Re: Testing CLI commands on Windows machines

Replies are listed 'Best First'.
Re^2: Testing CLI commands on Windows machines
by nysus (Parson) on Sep 12, 2018 at 15:02 UTC

    Thanks, always wondered what those were. Will look into using them. Continuously uploading to cpan to try to address problems with other platforms is getting old.</>

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

[reply]

      Since no one has mentioned it yet, stevieb has an excellent meditation on setting up Travis-CI for Perl development with multiple versions of perl. I've used his writeup as the starting point for all my CI.

[reply]

      It's pretty straightforward to setup, and really convenient in terms of getting emailed about failures and so on.

[reply]
        How is it different from cpan testers?
[reply]
Re^2: Testing CLI commands on Windows machines
by Anonymous Monk on Sep 12, 2018 at 09:11 UTC
    Whut ?
[reply]

      Which part of the post do you have problems understanding?

[reply]

In Section Seekers of Perl Wisdom