ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 10765] - junitreport stylesheet should include stdout/stderr
Date Sun, 14 Jul 2002 19:15:37 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10765>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10765

junitreport stylesheet should include stdout/stderr

sbailliez@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|cannot generate             |junitreport stylesheet
                   |system.out.println into     |should include stdout/stderr
                   |junitreport task            |



------- Additional Comments From sbailliez@apache.org  2002-07-14 19:15 -------
Ok, did not get that bug report was related to the xsl not using the output 
for the html report, there was a talk about parsing, formatter etc that has 
not much to do to me with the problem.

That said I'm partly convinced...the failed test just tell you that it 
failed... you should not need some print..this is what the debugger is for. :)

It's also that in the current state all you can do is to add a page with the 
output of all tests...you will barely be able to associate it to a given 
testcase unless you add some print here and there in the test methods...

Changing the summary to something more meaningful to me.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message