[
https://jira.codehaus.org/browse/SUREFIRE-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=341939#comment-341939
]
Max Calderoni commented on SUREFIRE-1066:
-----------------------------------------
Karl, thanks for checking: now i would like to reproduce your tests to see what
the difference is.
However, after cloning the link you provide,
https://github.com/khmarbaise/surefire, and doing 'mvn install' the two maven
projects require a parent, which i am not sure how to access...
Can you specify please?
<parent>
<groupId>com.soebes.smpp</groupId>
<artifactId>smpp</artifactId>
<version>0.6.3</version>
</parent>
> version 2.14.1 runs tests only if named *Test.java
> --------------------------------------------------
>
> Key: SUREFIRE-1066
> URL: https://jira.codehaus.org/browse/SUREFIRE-1066
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.14.1, 2.16
> Reporter: Max Calderoni
>
> This is a regression from 2.11, where it was working fine.
> For TestNG (and JUnit) tests, in order to be run by surefire, all you needed
> to do is to get the correct annotations in place (@Test) regardless of the
> name of your test classes.
> Looks like between version 2.11 and 2.14.1 surefire started *not* running
> classes whose name did not end with the word 'Test' (like it was few years
> back, when there were no annotations).
> That means that upgrading to 2.16 will break previous test code.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
