[ 
https://issues.apache.org/jira/browse/SUREFIRE-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716384#comment-14716384
 ] 

Tibor Digana commented on SUREFIRE-1152:
----------------------------------------

Current snapshot version has incomplete LazyTestSet implementation. It needs to 
be cachable. Without caching tests the rerun feature would not work properly. I 
have a fix in my local project which is part of larger feature SUREFIRE-580. 
The feature already works and supports reusable forks. So I need two days to 
support all three forking strategies, writing documentation and IT and sanity 
checks.
Then a deep testing of current features like rerun, test filtering 
(-Dtest=%regex[.*Test.*], includes/excludes) should continue.

Helpful would be the use of 2.19-SNAPSHOT in real projects and test all 
features.

> Option rerunFailingTestsCount silently fails with test suites
> -------------------------------------------------------------
>
>                 Key: SUREFIRE-1152
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1152
>             Project: Maven Surefire
>          Issue Type: Bug
>          Components: Maven Failsafe Plugin, Maven Surefire Plugin
>    Affects Versions: 2.18.1
>            Reporter: Sean Flanigan
>            Assignee: Tibor Digana
>             Fix For: 2.19
>
>         Attachments: flakyproject.zip
>
>
> After a test failure (with {{rerunFailingTestsCount > 0}}), the 
> {{JUnit4*Provider.executeWithRerun}} calls {{execute}} again with a list of 
> the failing {{testMethods}}, but {{JUnit4*Provider.execute}} silently fails 
> to find the requested methods.
> When {{testClass}} is actually a test suite class, it may not contain any 
> methods at all (other than inherited {{java.lang.Object}} methods).  The 
> {{execute}} method iterates through the {{java.lang.Object}} methods, never 
> finds a match for the {{testMethods}}, and silently fails to execute anything.



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

Reply via email to