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

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

From:
Matt Sergeant
Date:
August 28, 2001 06:49
Subject:
RE: [PATCH pod/perlhack.pod t/op/pack.t] Fixing bad testing advice
Message ID:
315E8A8BF9D1D411AD3D00508BB1B0C004B8FFB3@UKS040
> -----Original Message-----
> From: Robin Houston [mailto:robin@kitsite.com]
> 
> On Tue, Aug 28, 2001 at 02:18:55PM +0100, Matt Sergeant wrote:
> > make test TEST_VERBOSE=1
> > 
> > Shows you the line number where the test failed.
> > At least it does for me.
> 
> It doesn't do anything for me. I deliberately broke one of the tests
> in perl@10996/t/op/flip.t to test this, and:
> 
> bash$ make test TEST_VERBOSE=1
> ...
> op/flip............................FAILED at test 7
> ...
> Failed 1 test script out of 409, 99.76% okay.
>    ### Since not all tests were successful, you may want to run some
>    ### of them individually and examine any diagnostic messages they
> ...
> 
> 
> The caller() idea suggested by MJD and Nicholas Clark is good.

This is implemented in Test.pm, in core. Been there for a while now. That's
why I see line numbers I guess.

Matt.

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 www.star.net.uk



nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About