in reply to Relating Pert test report number to test items in the code

Why are you looking at the summary to find info about a specific test?

The test output should have been more like

a.t .. 1/4 # Failed test at a.t line 5. # got: '0' # expected: '2' # Looks like you failed 1 test of 4. a.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/4 subtests Test Summary Report ------------------- a.t (Wstat: 256 Tests: 4 Failed: 1) Failed test: 3 Non-zero exit status: 1 Files=1, Tests=4, 0 wallclock secs ( 0.02 usr + 0.03 sys = 0.05 CPU +) Result: FAIL Failed 1/1 test programs. 1/4 subtests failed.

Or if you gave your test a name:

a.t .. 1/4 # Failed test 'foo' # at a.t line 5. # got: '0' # expected: '2' # Looks like you failed 1 test of 4. a.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/4 subtests Test Summary Report ------------------- a.t (Wstat: 256 Tests: 4 Failed: 1) Failed test: 3 Non-zero exit status: 1 Files=1, Tests=4, 0 wallclock secs ( 0.01 usr + 0.00 sys = 0.01 CPU +) Result: FAIL Failed 1/1 test programs. 1/4 subtests failed.

In both case, it specifies the line number ("at a.t line 5"). If you provide a test name (2nd param for ok(), 3rd for is()), it provides that too ("Failed test 'foo'").

If you can't find the test even with the exact line number and the test name, your name is probably too generic.

Replies are listed 'Best First'.
Re^2: Relating Pert test report number to test items in the code
by ron7 (Beadle) on Feb 14, 2011 at 08:29 UTC
    Well don't I feel like a fool. All the failed tests I've looked at and never noticed/paid attention to the "# at <file> <line>" output!

    Thanks!