Re^3: organizing/ running non-module related tests

[graff]

If that's all you're doing, it's not such a big thing to roll on your own:

my @tests = sort <my/dir/*.pl>;  #update: need to sort the glob list
my $return = my $testid = 0;
while ( $return == 0 ) {
    warn "Running $tests[$testid]...\n";
    $return = system( $tests[$testid++] );
}

But learning to use MM is bound to be a good thing anyway, so why ask us whether you should do it?

update: if your scripts are actually moving data, then of course you'll need to prefix that loop with whatever steps are needed to clear out the destination db before the loop starts -- unless the first script in your list takes care of that.

[geektron]

each script clears out the relevant tables. because of foreign key constraints and such, i need to clean tables backwards, but i have that under control.

i'm asking if it's the right tool for the job, and as diotalevi pointed out, Test::Harness may in fact be better suited for what i'm trying to do.