Forum Discussion

subhaPrdhn's avatar
subhaPrdhn
Occasional Contributor
10 years ago
Solved

SOAP UI data driven testsuit's custom Junit report using plugin

:I have a problem generating custom JUnit report for SOAPUI Pro using com.github.redfish4ktc.soapui:maven-soapui-extension-plugin:4.5.1.0 plugin as my testsuits are data driven and have DataSource step (SOAP UI Pro feature) which is not recozinised in this plugin :womansad:
I can however generate default JUnit report using com.smartbear:ready-api-maven-plugin:1.5.0 which recoznises DataSource step.

 

How can i get a custom report with datasource as a step?
Attaching both my pom.xml.

 

Using ready-api-maven-plugin:

 

 

<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>test</groupId>
    <artifactId>ready-api-maven-plugin</artifactId>
    <packaging>jar</packaging>
    <version>1.0-SNAPSHOT</version>
    <name>Create SoupUI Application</name>
    <url>http://repo.maven.apache.org/maven2/</url>
    <pluginRepositories>
        <pluginRepository>
            <id>MavanSmartBearPluginRepository</id>
            <url>http://repo.maven.apache.org/maven2/</url>
        </pluginRepository>
		<pluginRepository>
            <id>SmartBearPluginRepository</id>
            <url>http://smartbearsoftware.com/repository/maven2/</url>
        </pluginRepository>
    </pluginRepositories>
	<properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
    </properties>
    <build>
        <plugins>
			<plugin>
			<groupId>com.smartbear</groupId>
			<artifactId>ready-api-maven-plugin</artifactId>
			<version>1.5.0</version>
				<dependencies>				
                    <dependency>
                        <groupId>net.sourceforge.jtds</groupId>
                        <artifactId>jtds</artifactId>
                        <version>1.3.1</version>	
			        </dependency>
					<dependency>
						<groupId>net.sourceforge.jexcelapi</groupId>
						<artifactId>jxl</artifactId>
						<version>2.6</version>
					</dependency>
					<dependency>
						<groupId>com.jgoodies</groupId>
						<artifactId>forms</artifactId>
						<version>1.0.7</version>
					</dependency>
					<dependency>
						<groupId>com.jgoodies</groupId>
						<artifactId>looks</artifactId>
						<version>2.2.0</version>
					</dependency>
            </dependencies>   
            <executions>
                 <execution>
                    <phase>test</phase>
                    <goals>
                        <goal>test</goal>
                    </goals>
                    <configuration>
                 	<projectFile>sampleProject.xml</projectFile>
					<outputFolder>${basedir}${file.separator}reports</outputFolder>
					<junitReport>true</junitReport>
					<exportAll>true</exportAll>
					<printReport>true</printReport>
 					<testSuite>${testsuite}</testSuite> 					 				
                    <soapuiProperties>
						<property>
							<name>script.logroot</name>
								<value>Log/</value>
						</property>
						<property>
							<name>soapui.home</name>
								<value>C:/Program Files/SmartBear/ReadyAPI-1.5.0/bin</value>
						</property>
                    </soapuiProperties>
                    </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
	<reporting>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-report-plugin</artifactId>
            <version>2.7.2</version>
        </plugin>
    </plugins>
</reporting>
</project>

 

Using maven-soapui-extension-plugin:

 

<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>test</groupId>
	<artifactId>ready-api-maven-plugin</artifactId>
	<version>1.0-SNAPSHOT</version>
	<name>Create SoupUI Application</name>

	<repositories>
		<repository>
			<id>maven2</id>
			<url>http://repo.maven.apache.org/maven2</url>
		</repository>
		<repository>
			<id>smartbearpluginRepository</id>
			<url>http://www.soapui.com/repository/maven2</url>
		</repository>
	</repositories>

	<pluginRepositories>
		<pluginRepository>
			<id>maven2</id>
			<url>http://repo.maven.apache.org/maven2</url>
		</pluginRepository>

		<pluginRepository>
			<id>smartbearpluginRepository</id>
			<url>http://smartbearsoftware.com/repository/maven2</url>
		</pluginRepository>
	</pluginRepositories>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
		<dep.version.soapui>4.5.1</dep.version.soapui>
	</properties>

	<dependencies>
		<dependency>
			<groupId>eviware</groupId>
			<artifactId>soapui</artifactId>
			<version>${dep.version.soapui}</version>
		</dependency>
		<dependency>
			<groupId>eviware</groupId>
			<artifactId>soapui-pro</artifactId>
			<version>${dep.version.soapui}</version>
		</dependency>
		<dependency>
			<groupId>eviware</groupId>
			<artifactId>ext-xmlbeans</artifactId>
			<version>1.2</version>
		</dependency>
		<dependency>
			<groupId>junit</groupId>
			<artifactId>junit</artifactId>
			<version>4.11</version>
		</dependency>
		<dependency>
			<groupId>com.github.redfish4ktc.soapui</groupId>
			<artifactId>maven-soapui-extension-plugin</artifactId>
			<version>4.5.1.0</version>
		</dependency>
	</dependencies>
	
	<build>
		<plugins>
			<plugin>
				<artifactId>maven-compiler-plugin</artifactId>
				<version>3.1</version>
				<configuration>
					<source>1.7</source>
					<target>1.7</target>
				</configuration>
			</plugin>
			<plugin>
				<groupId>com.github.redfish4ktc.soapui</groupId>
				<artifactId>maven-soapui-extension-plugin</artifactId>
				<version>4.5.1.0</version>
				<dependencies>
					<dependency>
						<groupId>test</groupId>
						<artifactId>ready-api-maven-plugin</artifactId>
						<version>1.0-SNAPSHOT</version>
					</dependency>
				</dependencies>
				<configuration>
					<runnerType>PRO</runnerType>
					<projectFile>sampleProject.xml</projectFile>
					<outputFolder>${basedir}${file.separator}reports</outputFolder>
					<junitReport>true</junitReport>
					<printReport>true</printReport>
					<exportAll>true</exportAll>
					<junitHtmlReport>true</junitHtmlReport>
					<soapuiProperties>
						<property>
							<name>soapui.logroot</name>
							<value>Logs/</value>
						</property>
 						<property> 
 							<name>soapui.junit.reportCollector</name>
 							<value>soapui.CustomJunitReportGenerator</value> 
 						</property> 
					</soapuiProperties>
				</configuration>
			</plugin>
		</plugins>
	</build>
</project>

 

3 Replies

  • Hello sasarode123 

     

    I have never had good outcomes by following documentation to add external jar files to:

      {smartbear install location}/bin/ext folder

     

    As long as there are no conflicting jar versions, I just go straight to including external jar files to:

      {smartbear install location}/lib folder

     

    If you only have a few (1 to 15 maybe) external jar files, this should not be a problem.  It gets a lot riskier (meaning, you have the potential to no longer make the application operate) if you have a lot of external jar files or conflicts with existing jar files.  You might have to trial and error a little bit however.  I use the date/time stamp as a quide to see what external jar files I might have added because those are usually different than the similarly dated files for the original install.  If you make the application (ReadyAPI or TestEngine) no longer operate, then remove the jars you added to /lib folder.  I have used that folder for years with success.

     

    Regards,

    Todd

    • sas's avatar
      sas
      Occasional Contributor

      Do you have a resolution to this question? I have a similar use case.

      • Hi sas, try checking out our documentation.

        I also recommend that you create a new topic where you can describe your use case in detail so that the Community could help you more efficiently.