Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

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.
    To do so, launch PowerShell as an administrator and execute the following command: Set-ExecutionPolicy RemoteSigned.
  • Create a Qualitia Offline Suite and the Offline Package.  For instructions on how to create an offline package, 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

In every machine where Qualitia client is installed, it contains the execution script at the following location:

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

This execution script has three different files:

  • arguments.ps1: To define the locations for the offline package, associated offline suite, and the reports folder.
  • master-configs.csv: To define various instances and their associated execution settings.
  • test-configs.csv: To map every test case with defined instance.


Configuring the Locations for Test Artifacts

To configure the location of test artifacts:

  1. Open the arguments.ps1  in a notepad editor.
    Enter the required information as shown in the following table.
Argument Description
$offlineEnter the absolute path for the Qualitia Offline Package. 
$suitepathEnter the location for the offline suite folder.
$logpathEnter the location for the folder where you want to save test case execution reports and logs.
$temppathEnter the location for the folder where you want to save the temporary files created during test case executions. 

 Enclose locations in quotation marks (" ").

Configuring the Confignames and Associated Parameters

Confignames are different instances of executions to override specific arguments as defined in the associated execution profile. 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 parameters one of the following ways:

  • Adding all the parameters in the arguments cell
  • Adding all the parameters separately in different columns

    Note: 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.


  1. Open the master-configs.csv file.
    This file contains all the master list of configurations. A configuration contains confignames and arguments under this configuration.

    Do one of the following: 

  • Adding All the Parameters in the arguments Cell 

    Under the arguments column, you can add all the values of parameters in the key=value format and separate parameters with a single space.

    The following screenshot is an example of adding arguments.

    • Adding all the Parameters Separately in Different Columns

     
    You need to define columns for each parameter for every configname . For every confignames, add values for each paarameter. 

    The following screenshot shows an example on how to add parameters for each setting.

     


Configuring the Test Cases 

  • Step 3: Open the test-configs.csv file in any CSV supported file such as MS-Excel.

For every test case, you can specify the instances.

You can combine the test cases from the Suite folder and the configurations from the master-configs.csv to execute test cases accordingly.

  1. Enter the A1 cell as TestCase_Name.
  2. Enter all the config names from the master-configs.csv in the top row.
  3. In the first column, from A2, enter the test case name and enter Y against each Confignnames as you want to execute. If you do not want execution on a Configname, specify as N.


    The following screenshot shows an example of how to add parameters for each setting.

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:

  1. Launch Windows PowerShell.
  2. Enter cd and the location of the execution scripts folder. For example, enter as cd C:\Qualitia\Scripts.
  3. 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. 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/Fail) to view the step-by-step report of test case execution.

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

  • No labels