[
https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798115#comment-16798115
]
Ilya Serbis commented on SUREFIRE-1527:
---------------------------------------
I think the issue should be converted to bug.
Just faced with it having my JUnit 5 tests been turned off silently.
In my case the cause was Groovy 2.5.5 It's
[POM|https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/2.5.5/groovy-all-2.5.5.pom]
has
{code:xml}
<dependency>
<groupId>org.codehaus.groovy</groupId>
<artifactId>groovy-testng</artifactId>
<version>2.5.5</version>
</dependency>{code}
which references {{org.testng:testng}}
The issue is still reproducible on the latest Surefire 2.22.1 and JUnit 5.4.1
(see demo project https://github.com/energister/surefire-1527)
> Surefire does not discover junit5 test case when testng is in the classpath
> ---------------------------------------------------------------------------
>
> Key: SUREFIRE-1527
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1527
> Project: Maven Surefire
> Issue Type: Improvement
> Components: JUnit 5.x support, TestNG support
> Affects Versions: 2.22.0
> Reporter: Dan Tran
> Priority: Major
>
> My maven module uses junit5 but also has testng in its test classpath and my
> surefire does not specify any testng.xml files
> Looks like surefire only look for testng test cases
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)