Re: [PR] differenciate between errors and failures for junit launcher [ant]

Vampire (via GitHub) <[email protected]>
Newsgroups gmane.comp.jakarta.ant.devel
Message-ID <PR_kwDOATT2FM6ZlEkp-aa691843-aad7-4451-ac36-3f1c0c85f62e@gitbox.apache.org>
Vampire commented on PR #221:
URL: https://github.com/apache/ant/pull/221#issuecomment-2954328450

   Hm, yeah, JUnit Platform indeed does not differentiate between failure and error anymore.
   I have no idea why, maybe @marcphilipp could shed some light on why this is not done anymore.
   
   Gradle indeed does also not do this differentiation yet, but reports both cases as failure.
   
   IntelliJ IDEA, when running the tests itself and not through Gradle delegation, does do the separation.
   
   Seems like a big cross-project inconsistency mess. :-(
   
   For me as user it was majorly confusing, that errors are reported as failures when using Ant, while when using IntelliJ IDEA integration they were shown as error.
   
   So maybe it is appropriate to follow suite with JUnit logic and not differentiate them.
   But then at least your own consumers of the file (the XSLs) should expect that it might be missing, as the generated HTML report looks broken if there is not even an errors attribute.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.