>>>> 2. Option to inject a clearcut delimiter between tests
>>>
>>> Distinct from, say, outputting a diagnostic between groups of tests?
>>
>> By 'tests' I'm thinking 'file' with its subtests, so-to-speak, so
yes,
>> anything that is clearly delineatable (LOL) programmatically where
one
>> 'file' output stops and another starts is fine.
>
>Different in what way from the current behaviour of Test::Harness?  
>Each test script gets its own line in the output currently.

Not if verbose output.

Surely you jest.  It is not reliably parsable, there can be garbage text
on the end of those summary lines at times.  If the harness was run from
one level above a 't' directory, you'll have t/ at the beginning of the
line, but what if not?  No way to predict the relative path someone will
use, how many '.....', or whether the last character on the line will be
a digit, ok, NOK, dubious, or whatever else, including just a dot.  Add
to that failed or died diagnostics.

Parse this to find the results per test to write them to db.  (This does
not take verbose into account where the challenge is more desperate).

somegreattestfoobars_exceptions..........ok
xwhateverr_exceptions....................ok 35/71
#     Failed test (xwhateverr_exceptions.t at line 1011)
xwhateverr_exceptions....................ok 71/71# Looks like you failed
1 test of 71.
xwhateverr_exceptions....................dubious
        Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 36
        Failed 1/71 tests, 98.59% okay
foobar_limit.............................ok 3/16
#     Failed test (foobar_limit.t at line 321)
foobar_limit.............................ok 16/16# Looks like you failed
1 test of 16.
foobar_limit.............................dubious
        Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 4
        Failed 1/16 tests, 93.75% okay


It would be healthy, smart, and advantagous for the good of TAP to add
an option for delimiter.

_____..._____ ~_~ _____..._____  <- kilroy?
somegreattestfoobars_exceptions..........ok
_____..._____ ~_~ _____..._____
xwhateverr_exceptions....................ok 35/71
#     Failed test (xwhateverr_exceptions.t at line 1011)
xwhateverr_exceptions....................ok 71/71# Looks like you failed
1 test of 71.
xwhateverr_exceptions....................dubious
        Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 36
        Failed 1/71 tests, 98.59% okay
_____..._____ ~_~ _____..._____
foobar_limit.............................ok 3/16
#     Failed test (foobar_limit.t at line 321)
foobar_limit.............................ok 16/16# Looks like you failed
1 test of 16.
foobar_limit.............................dubious
        Test returned status 1 (wstat 256, 0x100)
DIED. FAILED test 4
        Failed 1/16 tests, 93.75% okay
_____..._____ ~_~ _____..._____


That's all I have to say about that.  

-Forest Gump


The information contained in this message may be privileged, confidential, and 
protected from disclosure. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication is strictly prohibited. If you have received this 
communication in error, please notify us immediately by replying to the message 
and deleting it from your computer. 


Reply via email to