Introduction

A Parallel execution is a way of executing multiple instances for every test case of an offline suite simultaneously on different browsers, environments, and settings.

Qualitia provides a set of execution scripts to perform parallel execution of test cases using Windows PowerShell.

On This Topic:

Pre-Requisites

Windows PowerShell script execution policy must be set to RemoteSigned.
You need to launch PowerShell as an administrator and execute the following command: Set-ExecutionPolicy RemoteSigned.
Create an Offline package and the Offline Suite. For instructions on how to create an offline package and offline suite, refer to Offline Package.

You can execute Parallel Executions on Selenium Grid, but Selenium Grid cannot be used to manage the parallel executions.

Configuring the Execution Script for Parallel Execution

Every machine that has Qualitia Client contains the execution script used for parallel executions at the following location:

%LocalAppData%\QualitiaWDClient\app-x.x.x\Scripts

This execution script has the following three files:

arguments.ps1: To configure the locations for test artifacts: Offline Package, associated offline suite, and the reports folder.
master-configs.csv: To define Confignames and configure their settings.
test-configs.csv: To map every test case with the defined Confignames.

Configuring the Locations for the Associated Test Artifacts

You need to configure the location for the following test artifacts:

Offline Package: The software package that is used to execute the offline suites.
Offline Suite: The offline copy of a test suite that contains the test cases.
Reports: The test case execution results which also contains screenshots and the associated logs.

To configure the location for the associated test artifacts:

Open the arguments.ps1 in a text editor, such as Notepad or Notepad++.
Enter the required information as shown in the following table.

Argument	Description
$offline	Enter the absolute path for the Qualitia Offline Package.
$suitepath	Enter the location for the offline suite folder.
$logpath	Enter the location for the folder where you want to save test case execution reports and logs.
$temppath	Enter the location for the folder where you want to save the temporary files that are generated during test case executions.

Enclose locations in quotation marks (" ").

Configuring the Confignames

A Configname is a pre-defined set of configured settings used for a specific execution instance. For example, if you want a test case to execute on Internet Explorer 11, Firefox 76.x, Chrome 81.x, then you can define confignames such as IE_11, Firefox_76, and Chrome_81.

You can configure the settings of a Configname in one of the following ways:

Entering all the parameters in the arguments cell
Entering all the parameters separately in different columns

You need to open a json file of an execution profile located in the Execution Subfolder of offline suite folder. For example for defining a browser, type as BrowserName and browser as explorer, Google Chrome and Firefox.
If you do not specify any value to a specific parameter for a configname, then test cases are executed as per the associated execution profile.

To configure the Confignames:

Open the master-configs.csv file.
Enter as configname and arguments in the cells: A1 and B1.
To add values for settings of a configname, do one of the following:

To add all the parameters in the arguments Cell	Under the arguments column, add all the values of the settings in the key=value format and separate the parameters with a single space as shown in the following screenshot:
To add all the Parameters Separately in Different Columns	In the top row next to arguments, enter the name settings in each cell as defined in the execution profile json file. For every configname, add values for each setting as shown in the following screenshot: If you do not specify any value to a specific parameter for a configname, then test cases are executed as per the associated execution profile.

Mapping the Configured Confignames for Test Cases

For every test case, you need to map with the different Confignames.

To map the configured Confignames with Test Cases:

Open the test-configs.csv file.
Enter TestCase_Name in the A1 cell.
Under the TestCase_Name column, enter every name of test case of the offline suite in the same sequence.
Starting from B1, enter all the Confignames in each cell of the top row as you have defined in master-configs.csv.
For every test case, do the following:
- Enter Y against the Confignnames that you want to execute.
- Enter N against the Confignames that you do not want to execute.
  
  The following screenshot shows how to map confignames with test cases.

Parallel Execution of Test cases using Windows PowerShell

Ensure that you have configured the execution scripts to execute test cases using Windows PowerShell.

To execute test cases using Windows PowerShell:

Launch Windows PowerShell.
Enter cd and the location of the execution scripts folder. For example, enter as cd C:\Qualitia\Scripts.
Run the following command to start parallel execution for the test cases of the offline suite:
.\exec-parallel.ps1

Suite Execution Summary Report

After the test case execution completes, Qualitia generates a high-level summary report for the test cases executed in the specified environments (Confignames). You need to open the folder as the path specified by you in arguments.ps1.

The suite execution summary report displays the test case names and the number of total passed and failed test cases. You need to click the execution status Pass or Fail to view the test case execution report.

Here, Fail denotes the test case execution has failed or it has defects. Also, Not Executed denotes the execution did not start due to some technical reason or you have entered as No for the specific configname, in master-configs.csv.

The following screenshot shows how a parallel execution report is displayed.

You need to manually update a test case execution result in Real Time Reporting Portal. For more information, refer to U ploading a Test case or Test Suite Execution.

Browser not supported