Skip Menu |
 

This queue is for tickets about the Test-Harness CPAN distribution.

Report information
The Basics
Id: 17632
Status: resolved
Priority: 0/
Queue: Test-Harness

People
Owner: andy [...] hexten.net
Requestors: fperron [...] fxintegration.com
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 2.57_03
Fixed in: (no value)



Subject: diag output available in data structure
Download (untitled) / with headers
text/plain 1.1k
Hello there. I played with Test::TAP::Model to generate (html/xml) reports. I noticed that the 'diags' fields were not populated within the data structures. I wanted to have all the precious error codes and diag info logged somewhere... I also saw the patch to enable test script logging into a file-handle (did not try it yet, will try tomorrow...). Here is an observation: I traced the issue to within Test::Harness::Straps.pm around line 294 in the analyze_file sub (the pipe- open that reads-in a single test file for execution). I noticed that STDERR is vented out without much attention. Here are the questions: I decided to modify the pipe spec to "$line 2>&1 |", merging back all the output before analysis. Do you forsee any problem if I leave this merged output in there ? Is there anything simpler I could have done instead ? In the meantime, I created a proprietary module that 'use base Test::TAP::Model;' with a redefined 'analyze_file' method. This trick solves my problems. I just wanted to have insight into the potential pitfalls... Thanks, FX (linux-debian-sarge, perl 5.8.4, need to port this to win32/cygwin sometime soon...)
Download (untitled) / with headers
text/plain 143b
TAP 13 which is supported by Test::Harness 2.99 allows structured YAML diagnostics and Test::TAP::Model will be being updated to support them.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.