On 7/20/06, Gabor Szabo <[EMAIL PROTECTED]> wrote:
If I am not mistaken the problem with no_plan is that the test script
might exit before actually running all the tests you wanted and Harness
won't notice it.
That's what I wanted to avoid.
So maybe if there was a mode where Test::Builder did not automatically
print its counting but would wait for a call such as hey_finished_all_tests().
So this example that using no_plan wold succeed will actually fail.
use Test::More 'no_plan_but_wait';
ok(1);
exit;
ok(1);
hey_finished_all_tests();
I've pondered putting in a CORE::exit() override into Test::Builder
implicitly handle this problem, but some crazy people who think
they're writing C like to put "exit" at the end of their programs.
Some sort of "I'm done testing now" marker seems a way to go.
