Issue 85: ant integration: get it working properly with junitreport
Status:  Deprecated
Owner:
Closed:  Jan 2009
Cc:
Project Member Reported by marc.es...@gmail.com, Mar 10, 2008
currently, with the junit report output you don't see a really good
package/component/method hierarchy. instead, you get just a "package" and a
list of functions.

the reason is that junitreport is retarded and expects a single xml file
per test case. wtf they were thinking, i don't know. anyway, in order to
achieve the desired output, the ant runner would need to create a single
xml file per test case and not a single file per test suite.
Mar 11, 2008
Project Member #1 virtix
I'll take a wack at this after I get the webmaniacs preso done ...
Mar 22, 2008
Project Member #2 virtix
still on my radar. may bundle this up with the other ant todos
Status: Accepted
Apr 25, 2008
Project Member #3 virtix
Still thinking about this one. Been heads down in something related, xslt in ant. In
short, I think we can do better than what JUnit produces. So, instead of trying to
fit MXUnit into the JUnit report mold, I think for the same amount of effort, or
less, we can generate nicer reports and also bypass the whole <junitreport ...> task,
just continue to have outputdir an optional parameter in our task and then in
addition to generating xml, we can also generate the reports we want:
<mxutant server="localhost" port="80" outputdir="path/to/reports" ... > ...
Status: In
Cc: marc.esher
Apr 25, 2008
Project Member #4 marc.es...@gmail.com
i am not opposed to that in the least!!!
Jan 22, 2009
Project Member #5 virtix
I know we can do better. next gen anttask
Labels: Milestone-Release-2.0
Jun 30, 2010
Project Member #6 virtix
Moving some, but not all, of these to jira.mxunit.org
Status: Deprecated