maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tibor Digana (JIRA)" <>
Subject [jira] (SUREFIRE-1126) Discrepancy between test exclusion docs and plugin behavior
Date Mon, 02 Feb 2015 12:06:19 GMT


Tibor Digana commented on SUREFIRE-1126:

It is in progress
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
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

or the same with comma separated values.

class_pattern can be for instance pkg/, **/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:
>             Project: Maven Surefire
>          Issue Type: Bug
>    Affects Versions: 2.18
>            Reporter: Dima Spivak
>            Assignee: Tibor Digana
> According to [Surefire documentation|],
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

View raw message