[ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304595#comment-16304595 ]
ASF GitHub Bot commented on SUREFIRE-1416: ------------------------------------------ Github user Tibor17 commented on the issue: https://github.com/apache/maven-surefire/pull/143 @surli I had to change you code in new branch https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=shortlog;h=refs/heads/SUREFIRE-1416 Can you build the version `2.21.0-SNAPSHOT` using `mvn install -DskipTests` and let me know if the report site works for you? I want to include this fix in release in several days. > maven-surefire-parser: add new method isError in ReportTestCase > --------------------------------------------------------------- > > Key: SUREFIRE-1416 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1416 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Surefire Plugin > Reporter: Simon Urli > Priority: Minor > > There is currently no way after parsing test suite to know if a test case is > a failure or an error. I need a boolean isError in ReportTestCase and > associated getter and setter, to be able to use properly the > maven-surefire-parser API to know if a test is considered as an error or as a > failure, without consulting the logs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)