https://bz.apache.org/bugzilla/show_bug.cgi?id=69685
--- Comment #3 from Alex R. <[email protected]> --- > it might be more correct to follow suit with JUnit terminology and have the > `aborted` attribute and `<aborted>` tags. I'd like to make a contrary suggestion: Because you target JUnit 4 XML output (or "Legacy XML" output as JUnit now calls it), just count aborteds as skipped. JUnit does it iself. JUnit 5/6 supports two sets of formats and two different abstractions with it. One format is what the Jupiter test runner outputs, and its export format "Open Test Reporting". In there, they don't distinguish failures from errors (but handle both as "failed"), but distinguish dynamic skipping ("aborted") from static skipping ("disabled"), and also have a focus on containers, which aren't just aggregate results of their tests, but can have their own results (for example if a container fixture like AfterAll fails). The other format is JUnit 4 / "Legacy XML". When JUnit Jupiter exports this JUnit XML, they themselves convert aborted results to skipped results, split failed results into failures (if the exception derived from AssertionError) and errors (if not), and convert exceptions on container fixtures (BeforeAll, AfterAll) into exceptions for each of the container's tests [1]. [1] because the JUnit 4 XML format at its core deals in tests, and only uses suites for grouping them Since the junitlauncher task right now targets "legacy-xml", it should go all the way and output a JUnit XML with proper JUnit 4 abstractions. In fact, is it possible to directly leverage JUnit's Legacy XML export? When junitlauncher adds a target for JUnit 5/6 or Open Test Reporting, then it should export JUnit 5 abstractions. -- You are receiving this mail because: You are the assignee for the bug.
