[ 
https://jira.codehaus.org/browse/SUREFIRE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362359#comment-362359
 ] 

Tibor Digana edited comment on SUREFIRE-1126 at 2/2/15 6:06 AM:
----------------------------------------------------------------

It is in progress https://github.com/apache/maven-surefire/pull/83
I am fixing two issues actually SUREFIRE-745  and SUREFIRE-1126.
The point here is to unify the parser and use the same mechanism in junit4, 
junit47, and TestNG providers.
Nowadays the main functionality works, tests passed, but I need to update 
DirectoryScanner and DependenciesScanner due to %regex[] pattern.

As a result, the patterns will be

[!][class_pattern][[##method_pattern]]
or the same with comma separated values.

class_pattern can be for instance pkg/XTest.java, **/XTest, **/?Test, 
%regex[.*XTest.*], etc.
method_pattern can be for instance m?thod, test*, etc.

** denotes long path name or package
* denotes zero or more characters
? denotes single character


was (Author: tibor17):
It is in progress https://github.com/apache/maven-surefire/pull/83
I am fixing two issues actually SUREFIRE-745  and SUREFIRE-1126.
The point here is to unify the parser and use the same mechanism in junit4, 
junit47, and TestNG providers.
Nowadays the main functionality works, tests passed, but I need to update 
DirectoryScanner and DependenciesScanner due to %regex[] pattern.

As a result, the patterns will be

[!][class_pattern][[#method_pattern]]
or the same with comma separated values.

class_pattern can be for instance pkg/XTest.java, **/XTest, **/?Test, 
%regex[.*XTest.*], etc.
method_pattern can be for instance m?thod, test*, etc.

** denotes long path name or package
* denotes zero or more characters
? denotes single character

> Discrepancy between test exclusion docs and plugin behavior
> -----------------------------------------------------------
>
>                 Key: SUREFIRE-1126
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-1126
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.18
>            Reporter: Dima Spivak
>            Assignee: Tibor Digana
>
> According to [Surefire 
> documentation|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#test],
>  tests can be excluded on the command line by prefixing with an exclamation 
> mark. Is this expected behavior that's currently broken, or did someone jump 
> the gun with the docs?



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to