Disclaimer: this isn't just a cool use for/of Perl, it's a request to get some testers of an extremely easy to use app so I can hopefully get feedback.

NOTE: The current version this doc is based on is v0.05. I only uploaded it to CPAN a while ago, so it may not be indexed yet. Previous versions won't act according to this doc. You can either wait for it to be indexed, or fetch the zip/tarball file and install manually.

When I say easy to use, I mean it. If you have PerlBrew or BerryBrew installed and a module you've developed that's structured in a sane way:

cpan Test::BrewBuild
cd /path/to/MyModule
brewbuild

[download]

Output:

perl-5.8.9 :: PASS
perl-5.10.1 :: PASS
perl-5.22.1 :: PASS
perl-5.23.8 :: PASS

[download]

...yep, that's it. It'll run all of your unit tests across all of your currently installed *brew instances. We can get much deeper, however, I'll start with some explanations. I'm looking for feedback, so if you aren't interested in forking and submitting a PR or opening a bug report and it errors/warns on you, all you have to do is set a debug level and either post the output here, or email me at my CPAN email address.

brewbuild --debug 7
# or
brewbuild -d 7

[download]

This app/module works across both *nix and Windows, recognizes both ExtUtils::MakeMaker and Module::Build installers, and can be configured *very* easily with custom build plugins if neither of these work for you. I'll show the default plugin, then I'll provide an example of how to include your own.

Default bundled plugin:

package Test::BrewBuild::Plugin::DefaultExec;

sub brewbuild_exec {
        return <DATA>;
}

1;

__DATA__
if ($^O eq 'MSWin32'){
        my $make = -e 'Makefile.PL' ? 'dmake' : 'Build';
            system "cpanm --installdeps . && $make && $make test";
}
else {
        my $make = -e 'Makefile.PL' ? 'make' : './Build';
            system "cpanm --installdeps . && $make && $make test";
}

[download]

That's it. Unfortunately at this time, it's not possible via CLI args to include a non-installed plugin, so unless you want to write one to put on the CPAN, you just need to copy a CustomPlugin.pm file into ~/perl5/perlbrew/perls/*PERLVER*/lib/site_perl/*PERLVER*/Test/BrewBuild/Plugin directory. Then:

brewbuild --plugin 'Test::BrewBuild::Plugin::CustomPlugin'
# or just set the TBB_PLUGIN environment variable to make it persisten
+t

[download]

Using local plugins is imminent, just not there yet.

Now, here are some use cases. Note that all command line arguments have a single letter (ie. -d for --debug) shortforms:

Remove all existing *brew perl instances (less the one you may be using), install two new random versions, and test against all instances including the pristine ones:

brewbuild --remove --count 2

[download]

Run against all currently installed instances, and install one random new one and test against it too:

brewbuild --count 1

[download]

Install a few specific versions (use just the number portion from *brew available) and test against all installed:

brewbuild --version 5.20.3 -v 5.22.1 -v 5.8.9

[download]

The current documentation describes more situations, and you can read the docs for all installed pieces of the module here.

Note that ironically, I wrote this project to perform unit testing as I'm a huge stickler (I often have 100 times the number of lines of test code than I do code), but in this case, it has happened backwards. Don't worry, tests are coming fast and furious.

I wrote this module because Travis-CI doesn't perform tests on Windows. This module allows me to run my tests against all perl versions on both nix and Windows prior to putting it into the CPAN Testers wheelhouse.

Thanks for reading, and if you get a chance to test it out, I'd greatly appreciate any and all feedback.

Cheers,

-stevieb

In reply to Automate Perl/BerryBrew unit testing on Unix/Windows (Take 2) by stevieb

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.