develooper Front page | perl.perl5.porters | Postings from August 2001

RE: [PATCH pod/perlhack.pod t/op/pack.t] Fixing bad testing advice

Thread Previous | Thread Next
Matt Sergeant
August 28, 2001 06:19
RE: [PATCH pod/perlhack.pod t/op/pack.t] Fixing bad testing advice
Message ID:
> -----Original Message-----
> From: Robin Houston []
> Could you explain the advantage of having a "simple ok() function"?
> As somebody who has spent many painful hours debugging test failures,
> I'm intimately familiar with the _disadvantages_. When you run the
> test, you know that "test 113 failed". That's all you know, 
> in general.
> It's bad enough having to count the ocurrences of the ok() function to
> find out *which* test failed; and it's made considerably worse when,
> as is often the case, some of the ok()s are in loops.

make test TEST_VERBOSE=1

Shows you the line number where the test failed.

At least it does for me.

This email has been scanned for all viruses by the Star Internet Virus Screen.
The service is provided in partnership with MessageLabs, the email security company.
For more information on a higher level of virus protection visit

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About