maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SUREFIRE-1416) maven-surefire-parser: add new method isError in ReportTestCase
Date Thu, 11 Jan 2018 21:19:00 GMT

     [ https://issues.apache.org/jira/browse/SUREFIRE-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tibor Digana closed SUREFIRE-1416.
----------------------------------
    Resolution: Fixed

https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=869d6f29ff81bf2116a118f8118b63f21de4aa8a

> 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
>            Assignee: Tibor Digana
>            Priority: Minor
>             Fix For: 2.21.0.Jigsaw
>
>
> 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)

Mime
View raw message