https://bz.apache.org/bugzilla/show_bug.cgi?id=69685
Bug ID: 69685
Summary: `legacy-xml` listener should treat aborted tests like
skipped tests
Product: Ant
Version: 1.10.15
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P2
Component: Optional Tasks
Assignee: notifications@ant.apache.org
Reporter: bjo...@kautler.net
Target Milestone: ---
The `legacy-xml` listener that creates the JUnit XML file collects the aborted
tests separately from the skipped tests.
It writes an `<aborted>` tag as child of the `<testcase>` tag and has an
`aborted` count on the `<testsuite>` tag.
The problem is, that no typical consumer knows the `aborted` attribute or the
`<aborted>` tag.
Even your own `junitreport` task does not know either of them, so in the
resulting report there is nowhere an "aborted" count shown and the aborted
tests are listed with status "Success".
The "skipped" status means, that the test was skipped prior to even starting to
be executed like when using `@Ignore`.
The "aborted" status means, that the test was aborted after starting to run
like when using `Assumptions.assumeTrue(false)` from within the test, but never
to signal a failed and of course never to signal a successful test.
All other integrations I know treat aborted tests like skipped tests, as that
is usually what aborting means, some condition was checked in the beginning of
the tests and it was decided that the test should be skipped.
So I'd like to suggest, that aborted tests are recorded as skipped tests by the
`legacy-xml` listener, so that the typical consumers which only know success,
error, failure, and skipped can work properly with the result file, including
your own report generation XSL scripts.
--
You are receiving this mail because:
You are the assignee for the bug.
