Cross Project Testing

Purpose

• Cross project testing allows us to have end to end testing across multiple separate projects

Process

• The process of achieving end to end, cross project testing, involves:

  • Setting project name

  • Exporting the project as Jar

  • Importing in the end to end testing project

  • Integrating in end to end test

Setting project name

• We first set our project name, which acts as identifier for our project

• At resources-> properties -> global.property

  • project.name = projectname

• This will result in code generator to create references to our project to be used externally. Files created:

  • <projectname>Manager.java -> contains reference to panel methods and elements

  • <projectname>Data.java -> contains reference to data files

Export project

• We export our project as Jar file to be imported by other projects

• At automation -> pom.xml, set artifact id and group id for the project

  • 	<groupId>com.companyname</groupId>
    	<artifactId>autonomx</artifactId>
    	<version>1.0</version>
    	<packaging>jar</packaging>

• Export project at command line

  • mvn clean instal l-DskipTests

  • The Jar file will be created at automation -> target directory

Export to Jar repository

• Optionally we can export our project to a Jar repository, like Nexus or Artifactory

• We first set the url for the repository at automation -> pom.xml file

  • <repositories>
    		<repository>
    			<id>seleniumCore</id>
    			<name>vultr.guest-releases</name>
    			<url>http://artifact.autonomx.io/artifactory/libs-release-local</url>
    			<layout>default</layout>
    			<releases>
    				<enabled>true</enabled>
    			</releases>
    			<snapshots>
    				<enabled>true</enabled>
    			</snapshots>
    		</repository>
    	</repositories>

• We then set the version at the top of the pom.xml 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>io.autonomx</groupId>
    	<artifactId>autonomx</artifactId>
    	<version>1.0.1</version>
    	<packaging>jar</packaging>	

  • We need to increment the version at each deploy. eg. 1.0.1, 1.0.2, 1.0.3...

• At command line we depoy

  • mvn deploy

  • This will upload the jar and the source to the Jar repository

Import Jar At Target Project

Import Local Jar

• If we want to import the created Jar locally without using the Jar repository, we can add the dependency at pom.xml file under the dependency section

  • <dependency>
    		    <groupId>io.autonomx</groupId>
    		    <artifactId>autonomx</artifactId>
    		    <version>1.0.1</version>
    		    <scope>system</scope>
    		    <systemPath>${project.basedir}/library/autonomx-1.0.jar</systemPath>
    </dependency>

Import From Jar Repository

• We can import from jar repository by adding the dependency int he pom.xml file

  • 	<dependency>
    			<groupId>io.autonomx</groupId>
    			<artifactId>autonomx</artifactId>
    			<version>1.0.1</version>
    		</dependency>

End To End Test

• We can then call the imported project's panel methods and elements

  • @Test(description = "uses module manager and data class created through project.name")
    	public void verifyCrossProjectManager() {
    		
    		autonomxManager autonomx = new autonomxManager();
    		User user = autonomxData.webApp.user().admin();
    		autonomx.webApp.login.loginWithCsvData(user);
    	}

  • Here, autonomxManager is <project.name>Manager

    • With autonomxManager we can access all methods and elements the same way as we do using "app." in our current project

  • autonomxData is <project.name>Data class, giving us access to all data files