Maven: Running TestSuite Tests run: 0

25 views
Skip to first unread message

Ravi Mangala

unread,
May 29, 2016, 11:20:10 AM5/29/16
to Jenkins Users
Hi Team,

I am working on integration of Selenium webdriver with Jenkins using Maven.

When I run mvn test I am getting Running TestSuite Tests run: 0.

My POM file:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>project</groupId>
    <artifactId>project</artifactId>
    <version>0.0.1-SNAPSHOT</version>

    <repositories>
        <repository>
            <id>dev</id>
            <url>http://rmr.qa/repository/dev/</url>
        </repository>
    </repositories>
    <build>
        <sourceDirectory>src</sourceDirectory>
        <testSourceDirectory>${base.dir}\src\</testSourceDirectory>
        <resources>
            <resource>
                <directory>src</directory>
                <excludes>
                    <exclude>**/*.java</exclude>
                </excludes>
            </resource>
        </resources>
        <testResources>
            <testResource>
                <directory>${base.dir}\src\test\</directory>
                <includes>
                    <include>**\*.java</include>
                </includes>
            </testResource>
        </testResources>
        <plugins>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.3</version>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.4.3</version>
            </plugin>
        </plugins>
    </build>
    <dependencies>
        <dependency>
            <groupId>org.seleniumhq.selenium</groupId>
            <artifactId>selenium-java</artifactId>
            <version>2.48.0</version>
        </dependency>
        <dependency>
            <groupId>org.seleniumhq.selenium</groupId>
            <artifactId>selenium-server</artifactId>
            <version>2.33.0</version>
        </dependency>
        <dependency>
            <groupId>org.junit</groupId>
            <artifactId>junit</artifactId>
            <version>1.0</version>
        </dependency>
        <dependency>
            <groupId>org.testng</groupId>
            <artifactId>testng</artifactId>
            <version>6.9.9</version>
        </dependency>
        <dependency>
            <groupId>log4j</groupId>
            <artifactId>log4j</artifactId>
            <version>1.2.17</version>
        </dependency>
        <dependency>
            <groupId>net.sourceforge.jexcelapi</groupId>
            <artifactId>jxl</artifactId>
            <version>2.6.12</version>
        </dependency>
        <dependency>
            <groupId>javax.mail</groupId>
            <artifactId>javax.mail-api</artifactId>
            <version>1.5.5</version>
        </dependency>

    </dependencies>

</project>

Karl Heinz Marbaise

unread,
May 29, 2016, 11:32:19 AM5/29/16
to jenkins...@googlegroups.com
Hi,


First what I see is that you changing the default folder layout which is
in general a bad idea...

Just remove all the configuration for
sourceDirectory/testSourceDirectory etc. / resources filtering /
includes/excludes...
Apart from that java class are no resources...for those things
src/test/resources exists...to put property files into etc. which are
available on the classpath...

go with the defaults...

Put your test classes into src/test/java/... and follow the naming
conventions *Test.java etc.

Furthermore define an more uptodate maven-surefire-plugin (2.19.1)...

And of course use an uptodate version of junit:

<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.12</version>
</dependency>

Furthermore you should make a decision which unit test framework you use
for writing tests. Based on the character those tests have (selenium)
which are integration tests i would prefer testng ...and so only a
single dependency either junit or testng is the best not both...

Conclusion: This is more a question for the maven users list than for
the jenkins users list...

Kind regards
Karl Heinz Marbaise

Ravi Mangala

unread,
May 29, 2016, 12:10:48 PM5/29/16
to Jenkins Users, in...@soebes.de
Thanks Karl,

I will do as you suggested.

Thanks again for quick reply.
Reply all
Reply to author
Forward
0 new messages