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-1311) JUnit47 provider should not internally parse JUnit Description
Date Fri, 02 Dec 2016 03:39:59 GMT

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

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

https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=d9b577cdc991d09116282d89ca69b5d2768acb0e

> JUnit47 provider should not internally parse JUnit Description
> --------------------------------------------------------------
>
>                 Key: SUREFIRE-1311
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1311
>             Project: Maven Surefire
>          Issue Type: Task
>          Components: Junit 4.7+ (parallel) support, Maven Failsafe Plugin, Maven Surefire
Plugin
>            Reporter: Tibor Digana
>            Assignee: Tibor Digana
>             Fix For: 2.19.2
>
>
> We used regex pattern to parse JUnit Description from string form to (className and methodName)
in provider {{surefire-junit4}}.
> The provider {{surefire-junit47}} inherited the same principle which is wrong because
JUnit 4.6 already has this parser inside and we should call {{Description.getClassName()}}
and {{Description.getMethodName()}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message