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 32745] - JUnitReport does not handle multiple reports from the same testcase.
Date Mon, 21 Feb 2005 13:16:55 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32745>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32745





------- Additional Comments From yves.martin@elca.ch  2005-02-21 14:16 -------
No.

A custom stylesheet uses the aggregated XML TESTS-TestSuites.xml in which I've
just added the 'id' attribute. So backward compatibility is OK.

In case a custom stylesheet should address the bug issue (multiple same
testsuites), it may uses the 'id' - but it is really optional. With current
status, the bug cannot be addressed by a stylesheet.

For example, the 'junit-noframes.xsl' is unchanged because it processes the XML
without expected package/name 'testsuite' attributes to be a unique key. 
junit-frames.xsl has to use a unique key because it generates many files linked
together: package index, classes index, -out.txt and -err.txt. My patch proposes
to use id/package/name as a key.

If another processing uses the generated report as input (which is strange
because it is easier to process TESTS-TestSuites.xml), it is true that such a
processing has to be updated. But I think it is not in the 'junitreport' contract.


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message