So According to http://perl.apache.org/docs/general/testing/testing.html#C_Apache__TestSmoke__Solution
The sample t/SMOKE.PL files is:
#file:t/SMOKE.PL #--------------- #!perl
use strict; use warnings FATAL => 'all';
use FindBin; use lib "$FindBin::Bin/../Apache-Test/lib"; use lib "$FindBin::Bin/../lib";
use Apache::TestSmoke ();
Apache::TestSmoke->new(@ARGV)->run;
That uses TestSmoke, not TestSmokePerl [directly] like I would expect
That's what I currently have in my t/SMOKE.PL [sans FindBin stuffs].
I tried using a t/SMOKE.PL that used TestSmokePerl instead of TestSmoke. It wasn't pretty. :-)
And maybe that's my issue.
After looking at it again, I get the feeling that t/SMOKE for an A-T dist using mod_perl really wants to use TestSmokePerl instead of TestSmoke; and TestSmokePerl looks much much thinner than TestRunPerl in terms of the mod_perl configuration steps in the module.
Assuming it's the right thing to do, adding the mod_perl config stuff into TestSmokePerl from TestRunPerl shouldn't be too difficult.
I'm afraid of breaking anything that uses TestSmokePerl, but it doesn't appear like much, if anything does?
-=Chris
smime.p7s
Description: S/MIME Cryptographic Signature
