Maven – Running TestNG tests in Maven fails

maventestng

I am trying to run TestNG tests in Maven. here is my configuration:

pom.xml:

     <dependencies>
             <dependency>
        <groupId>org.testng</groupId>
        <artifactId>testng</artifactId>
        <version>6.3.1</version>
        <scope>test</scope>
    </dependency>
</dependencies>
<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.11</version>
            <configuration>
                <suiteXmlFiles>
                    <suiteXmlFile>src/test/resources/testng.xml</suiteXmlFile>
                </suiteXmlFiles>
            </configuration>
        </plugin>
    </plugins>
</build>

This is the testNG conf file:

<suite name="Suite1">
<test name="Test1">
    <groups>
        <run>
            <include name="Setup" />
            <include name="Material" />
        </run>
    </groups>

    <packages>
        <package name="coloright.hibernate.*" />
    </packages>
</test>

when I run with eclipse – no problem.

when I run with mvn test – all test run successfully, but build failed with error:

suiteXmlFiles is configured, but there is no TestNG dependency

Please help

Best Answer

Looks like you are hitting this surefire bug, which contrary to the status looks to be still open.

The bug appears if surefire is unable to find the file specified in <suiteXmlFile>. Could you try just specifying testng.xml omitting src/test/resources to see if that helps? The documentation is silent on how this location is to be specified - whether it should be relative to the base directory or relative to test resources folder.

Related Solutions

Java – How to add local jar files to a Maven project

You can add local dependencies directly (as mentioned in build maven project with propriatery libraries included) like this:

<dependency>
    <groupId>com.sample</groupId>
    <artifactId>sample</artifactId>
    <version>1.0</version>
    <scope>system</scope>
    <systemPath>${project.basedir}/src/main/resources/Name_Your_JAR.jar</systemPath>
</dependency>

Update

In new releases this feature is marked as deprecated but still working and not removed yet ( You just see warning in the log during maven start). An issue is raised at maven group about this https://issues.apache.org/jira/browse/MNG-6523 ( You can participate and describe why this feature is helpful in some cases). I hope this feature remains there!

If you are asking me, as long as the feature is not removed, I use this to make dependency to only one naughty jar file in my project which is not fit in repository. If this feature is removed, well, there are lots of good answers here which I can chose from later!

Java – Spring-Autowiring happens after @BeforeClass when running test with maven-surefire

Additionally, until this issue is fixed, if things still aren't working for you after following the previous advice OR you do not wish your code to be executed before every single method, then add the following code to your test class:

@Override
@BeforeSuite
protected void springTestContextPrepareTestInstance() throws Exception {
    super.springTestContextPrepareTestInstance();
}

This ensures that the Spring Context will be prepared before your @BeforeClass methods are executed.

*note, I posted this answer since in the title you're asking about @BeforeClass, even though there is no usage of @BeforeClass in your sample code.

Best Answer

Related Solutions

Java – How to add local jar files to a Maven project

Java – Spring-Autowiring happens after @BeforeClass when running test with maven-surefire

Related Topic