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 Mon, 15 Jul 2002 04:12:18 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





------- Additional Comments From jtmolecule@hotmail.com  2002-07-15 04:12 -------
I'm the original submitter.  We are writing junit tests to perform some 
testcases, and if it's successful, it would be more informative to know which 
successful test cases were performed, rather than just seeing the 
word "success" on the html page.  That way, there can be an audit on which 
tests were performed without looking at the code.  At least with the fail
(String) and assertEquals(String, *, *), we can print something out to say what 
failed, but if it's successful, there is no trail on which ones became 
successful.

The std-out and std-err is for the whole page and not for individual testXXX 
methods.  Besides, I tried have a System.out.println() statement, and nothing 
showed up on the html page.

Thanks for your feedbacks.

--
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