On Feb 8, 2006, at 11:41, Geoffrey Young wrote:
so, I guess my question is whether the plan->is linkage can be
broken in
Test::Builder/Test::Harness/wherever and still keep the bookkeeping in
tact so that the library behaves the same way for the bulk case. or
maybe at least provide some option where calls to is() don't bork out
because there's no plan (and providing an option to Test::More
where it
doesn't send a plan header).
so, thoughts or ideas? am I making any sense?
Yes, you are. I think that the subprocess can load Test::More and
friends like this:
use Test::More no_plan => 1;
Test::More->builder->no_header(1);
That will set No_Plan, Have_Plan, and No_Header to true, silencing
the "Gotta have a plan!" error and the "1.." message at the end.
HTH,
David
