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 49 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.
    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 configure the Configames with settings used for test case executions.
  • 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:

  1. Open the arguments.ps1  in a notepad editor.
  2. 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 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:

  1. Open the master-configs.csv file.
  2. Enter as configname and arguments in the cells: A1 and B1.
  3. To add values for settings of a configname, do one of the following: 
    1. Adding All the Parameters in the arguments Cell 
      1. Under the arguments column, you can add all the values of the settings in the key=value format and separate parameters with a single space.
        The following screenshot shows how to add multiple settings in the arguments column.

  1. Adding all the Parameters Separately in Different Columns

 

Do the following in the order listed:

  1. In the top row next to arguments, enter the name settings in each cell as defined in the execution profile json file.
  2. For every configname, add values for each setting. 

    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.

    The following screenshot shows how to add values in each setting.

     


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:

  1. Open the test-configs.csv file.
  2. Enter TestCase_Name in the A1 cell.
  3. Under the TestCase_Name column, enter every test case name of the offline suite.
  4. Starting from B1, enter all the Confignames in each cell of the top row as you have defined in master-configs.csv.
  5. 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:

  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 (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 failed or has defects. Also, Not Executed denotes the execution did not happen or you did not want for the specific configname.

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 Uploading a Test case or Test Suite Execution.

  • No labels