You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Tran (JIRA)" <ji...@apache.org> on 2018/07/01 09:05:00 UTC

[jira] [Comment Edited] (SUREFIRE-1527) Surefire does not discover junit5 test case when testng is in the classpath

    [ https://issues.apache.org/jira/browse/SUREFIRE-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529019#comment-16529019 ] 

Dan Tran edited comment on SUREFIRE-1527 at 7/1/18 9:04 AM:
------------------------------------------------------------

Here is proposed fix at TestNgProviderInfo
{code:java}
    @Override
    public boolean isApplicable()
    {
        return testNgArtifact != null && hasSuiteXmlFiles();
    }{code}


was (Author: dantran):
Here is proposed fix at TestNgProviderInfo

{code}

    @Override
    public boolean isApplicable()
    {
        return testNgArtifact != null && hasSuiteXmlFiles();
    }

{code>

 

Another workaround to force surefire not able to detect the present of testng
{code:java}
<configuration>
    <testNGArtifactName>org.testng:testng-ignore</testNGArtifactName> 
</configuration>{code}

> 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)