On 21/07/06, chromatic <[EMAIL PROTECTED]> wrote:
On Thursday 20 July 2006 16:01, Michael G Schwern wrote:
> 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.
> PS In all my years of testing I have never been bitten by this in the
> real world which is why I've never bothered to code up a solution.
> Anyone else?
Test an XS component. Segfaults don't call done_testing_now().
Yes, that happened to me last night. Yes, I had 'no_plan' active. Yes, I
noticed it as a happy accident, thinking "That test number looks awfully
low."
My first thought was also XS and segfaults. Then I tried it
$ perl -le 'print system("./segfault")'
11
Test::Harness should pick this up. If the exit code is not a multiple
of 256 then the program didn't exit normally,
F
