On Wed, Nov 7, 2012 at 2:23 AM, John M. Gamble <jgam...@ripco.com> wrote:
> I have tests in a module that take a long time to run. Strictly speaking,
> the CPAN testers don't need to run all of them, so it makes sense to have
> them automatically skipped, letting me run them manually when I want.

The AUTHOR_TESTING or RELEASE_TESTING environmental variables are the
standard [1] means to get what you want.

> Reading the Module::Build::API document, I see that I can create my own
> option (e.g., --Testall) using the get_options parameter. But it looks
> like I can only pass information to the test files via tap_harness_args
> to TAP::Harness.  Currently, all but two of my test files use Test::Simple,
> with the remaining files using Test::More.
>
> Do I have to re-write my test files to use TAP::Harness?

No, you don't. TAP::Harness is the TAP consumer, that checks and
summarizes the test results. Test::{Simple,More} is the TAP producer,
that outputs its result. They are decoupled.

[1]: http://use.perl.org/use.perl.org/_Alias/journal/36128.html

Leon

Reply via email to