Steve Loughran wrote:
What I propose is that, in order to avoid destroying information, Surefire
should generate XML that looks like Example 7 (all-in-one-file), and not
try to fake it to look like Example 2 (one-file-per-class). (TestNG's
junit-like output also generates files like Example 7.) However, when it
comes time to generate an HTML report, surefire-reports will discard
suite-level information, and treat large suites like Example 7 as if they
had been presented in separate files like Example 2. I'd argue that all
of the other JunitReport-like tools (including Ant) should probably follow
the same lead.
I think that if everyone else has a bug, its hard to call it a bug. More
a presentation choice :)
I'd thought somebody might say that! :-) Still, do you think TestNG and
other tools should therefore generate multiple XML files, to be compatible
with the other (arguably broken) reporting tools?
-Dan
