> from the runner, something would still need to be able to aggregate those > reports across multiple runs (ie: "ant test" being run in multiple dirs,
That's correct. > Thinking about it purely from the point of view of the failure rate > reports i've been generating, it would be nice if *every* TestClass > invocation consistently included a single psuedo-method entry [...] The thing is this would probably break things elsewhere. Those XMLs reports, although not specified anywhere, are accepted by a range of tools and my xml listener just tries to mimic closely what Apache Ant and Apache Maven emit in similar circumstances. I wonder what happens if you had a project with a regular maven/ ant test output and executions of multiple instances of the same class... I probably cross-checked it when I was trying to mimic their output, but I bet it wasn't anticipated as a possible scenario... Another possibility would be to try to correct those aggregations of individual XML reports in Jenkins so that the output is easier to post-process... Don't know, really. It is a mess. D. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
