Id like to propose that I (or someone like me) add a passthru option
which lets someone pass thru options and arguments to the test scripts being run.
The idea is to support 'torture' testing as it is typically (I think) done now.
and not coincidentally ...
[EMAIL PROTECTED] added ext/B/t/OptreeCheck.pm, which added command-line argument handling, and which would benefit from passthru support.
prove --passthru testmode=cross ext/B/t/optree_*
for example:
[EMAIL PROTECTED] bleadperl]$ ./perl -Ilib ext/B/t/optree_samples.t help
ext/B/t/optree_samples.t accepts args to update these state-vars:
turn on a flag by typing its name,
select a value from list by typing name=val.
$VAR1 = {
'dump' => 'dump cmdline arg prcessing',
'fail' => 'force all test to fail, print to stdout',
'help' => 0,
'retry' => 'retry failures after turning on re debug',
'retrydbg' => 'retry failures after turning on re debug',
'rexpedant' => 'try tighter regex, still buggy',
'rextract' => 'writes src-code todo same Optree matching',
'selfdbg' => 'redo failing selftests with re debug',
'selftest' => 'self-tests mkCheckRex vs the reference rendering',
'testmode' => [
'native',
'cross',
'both'
],
'vbasic' => 'prints $str and $rex',
'xtest' => 'extended thread/non-thread testing'
};
ext/B/t/optree_samples.t heres current state:
$VAR1 = {
'dump' => 0,
'fail' => 0,
'help' => 1,
'retry' => 0,
'retrydbg' => 0,
'rexpedant' => 0,
'rextract' => 0,
'selfdbg' => 0,
'selftest' => 0,
'testmode' => 'native',
'vbasic' => 0,
'xtest' => 0
};
The whole OptreeCheck argument handling scheme sort of jumps the gun on a standardized treatment of test-script-arguments. IOW, I couldnt discern a current standard way, so I constructed one in hopes of conver[sg]ing toward a GWTDI.
Before I embark on this (short --passthru trip), Id like to hear that its not a dumb idea.
thx jimc
