Cross-Application Testing

From the Quantum V9 ServicePack 3 release, App Factory has added support to run tests across multiple apps. From the V9 ServicePack 5 release, you can run cross-app tests for Native channels. You can also run tests across Quantum apps and non-Quantum apps.

IMPORTANT:
For Quantum versions V9SP4 or earlier, App Factory supports cross-app testing only with the Jasmine test framework for the Web channel.

For more information, refer to the Cross-Application Testing section in the Visualizer User Guide.

Testing Across Quantum Apps

To run cross-application tests across Quantum Apps, you need to place the Jasmine Integration Test resources within the source of the base app in the SCM. For more information, refer to the folder structure in the following image.

For more information about the files and folders that are required for Jasmine integration tests, refer to the Cross-Application Testing section in the Visualizer User Guide.

IMPORTANT:
  • Make sure that the dependent apps are built in the test mode and are deployed at URLs that are accessible by App Factory.
  • During every test run, the protocol and ScriptURL keys in the IntegrationTests.json file are overwritten based on the run-time values.

Testing Across Quantum and non-Quantum Apps

You can use Selenium automation to test apps and widgets that are not part of Quantum, for example, a third-party login from a web browser. To integrate Jasmine tests with Selenium automation, you must implement a Java interface and the respective methods. You also need to use the Cross-App Testing APIs to connect to a WebSocket and exchange messages between the Jasmine and Selenium frameworks.

The test resources for Selenium automation must be placed as a Maven project at the following path: <Visualizer Project>/testresources/TestNG/SeleniumIntegrator/. After implementing the interface and the methods, the Java file must be stored at the following path: <Visualizer Project>/testresources/TestNG/SeleniumIntegrator/src/main/java/com/temenos/user/wsclient.

For more information, refer to the folder structure in the following image.

For more information about the Java interface and methods, refer to the following sections.

This interface must be implemented to integrate the Selenium automation code with the Jasmine tests. It can also be used to add automation capabilities for apps and widgets that are not part of Quantum.

The interface contains two key methods: onMessage and onInitDriver, which must be implemented along with the code that is executed when a message is received from the Jasmine framework. You can use Cross-App Testing APIs to connect to a WebSocket and to exchange messages between the Jasmine and Selenium frameworks.

The interface also contains the getDriverCapabilities method, which can be used to override a set of driver capabilities.

During the run time, App Factory identifies the class that implements this interface, and then invokes the onInitDriver method to fetch the driver object.

Syntax

public interface CrossAppClientInterface

The App Factory CI Pipeline invokes this method when it receives a message from the Jasmine framework. This method passes the message (JSONObject) from the Jasmine framework to the Selenium framework, and returns a message (JSONObject) to the Jasmine framework.

Syntax

public JSONObject onMessage(JSONObject Object)

Parameters

Object [JSONObject]
Specifies the message that is received from the Jasmine framework during the run time.

Return Type

JSONObject
Specifies the message that must be passed to the Jasmine framework during the run time.

IMPORTANT:
If you are using Quantum version V9SP4 or earlier, the name of this method is onInitWebDriver.

The App Factory CI Pipeline invokes this method after it creates the driver object; the type of the object is based on the platform. Make sure that you check the type of object before assigning it to a variable.

Platform Object Type

Android

AndroidDriver

iOS

IOSDriver

Web

ChromeDriver

Syntax

public void onInitDriver(WebDriver driver);

Parameters

driver [WebDriver]
Specifies the driver object that is sent by the App Factory CI pipeline after initialization.

Return Type

void

Sample code: Check platform and object type

//For the web platform
if (driver instanceof ChromeDriver)
{
	myDriver = (ChromeDriver) driver;
}
else
{
	System.out.println("Wrong driver is initialised.");
}

//For the Android platform
if (driver instanceof AndroidDriver)
{
	myDriver = (AndroidDriver) driver;
}
else
{
	System.out.println("Wrong driver is initialised.");
}

//For iOS platform:
if (driver instanceof IOSDriver)
{
	myDriver = (IOSDriver) driver;
}
else
{
	System.out.println("Wrong driver is initialised.");
}

The App Factory CI Pipeline invokes this method before creating the driver object. You can use this method to override a set of capabilities.

App Factory supports overriding the following capabilities:

  • orientation
  • printPageSourceOnFindFailure

Syntax

default Map<String, Object> getDriverCapabilities()

Parameters

None.

Return Type

Map<String, Object>
Specifies a map of capabilities with the capability name as key and the capability value as value.

Backward Compatibility with Quantum Visualizer

  • For Web channels
    • 9.2.29 (or later)
  • For Native channels
    • 9.2.49
    • 9.3.24
    • 9.4.8 (or later)

Running a Cross-Application Test

After you add the test resources for the dependent apps to the directory of the base app, you can run cross-app tests by running a Jasmine test on the base app. For more information, refer to Testing an App with the Jasmine Test Framework.

Test Results

After the Jasmine tests are successfully executed at the run time, App Factory generates separate test results for every time an app is launched. The test results can be identified by the app name and the time-stamp, for example, TestResult_App2_12-03-2021_05-56-46.html.

The recipients that are added to the recipients list in the Project Settings will receive an email notification with links to the test results.