[
https://issues.apache.org/jira/browse/SUREFIRE-1185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969225#comment-14969225
]
Tibor Digana commented on SUREFIRE-1185:
----------------------------------------
This was intended if method filter appears because of the DirectoryScanner
complexity.
As a reason we have to spawn the forked jvm with all tests if a negative filter
is found and there this behavior will not change.
I will think about how we can improve it.
> single method test spews status of every single other test
> ----------------------------------------------------------
>
> Key: SUREFIRE-1185
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1185
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.18.1
> Environment: windows/linux/mac
> Reporter: Dan Tran
>
> here is a sample
> $ mvn -Dtest=rest/DataSourceTest#testPutNullType
> Running com.xxx.xxx.xxx.rest.TagCategoryTest
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in
> com.xxx.xxx.xxx.rest.TagCategoryTest
> ....
> Found at both surefure 2.18.1 and 2.19
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
