exec is enough to make me think this is a bad idea. And there are other reasons why this wouldn't really address the "problem".

Instead write Test::AutoPlan that you use like: 

perl -MTest::AutoPlan -e0 t/*

[download]

and it would run each of your t/* files and then modify them to record the current plan count, notifying you how the counts had changed.

Instead of writing your t/* files like: 

use Test::More ( ... );
...

[download]

you'd write them like: 

use Test::AutoPlan qw( Test::More ... );
...

[download]

and perl -MTest::AutoPlan t/* would change that to 

use Test::AutoPlan 23 qw( Test::More ... );
...

[download]

and you could even make it so "make plan" updates the test count plans.

The Test::AutoPlan code goes something like this: 

my $plan;

sub VERSION {
    $plan = $_[1];
}

sub import {
    my $self = shift(@_);
    goto &UpdateTests   if  ! @_;
    my $module = shift(@_);
    my @plan = "no_plan";
    if(  defined($plan)  ) {
        @plan = ( tests => $plan );
    } elsif(  "Test::Simple" eq $module  ) {
        @plan = ( tests => 0 );
    }
    unshift @_, $module, @plan;
    my $import = $module . "::import";
    undef $plan;
    goto &$import;
}

sub UpdateTests {
    for my $test ( @ARGV ) {
        my $plan = RunTestsAndCount( $test );
        @ARGV = $test;
        $^I = ".old";
        while( <> ) {
            s{
                ^(
                  [\w\s]*
                  (?<![\w:])
                  Test::AutoPlan
                )
                (\s+\d+)?
            }{
                $1 . " " . $plan
            }ex;
            print;
        }
    }
}

[download]

The first argument could be Test::Simple instead of Test::More (or whatever other modules you decide to support).

- tye        

In reply to Re: How can I write Test::Finished? (auto count) by tye
in thread How can I write Test::Finished? by samtregar

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.