Pre-Requisites

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

Configuring the Execution Script for Parallel Execution

Anchor
ConfiguringExecutionScript ConfiguringExecutionScript

In every Every machine where Qualitia client is installed, it 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 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.

To configure the location of 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:

1. Open the arguments.ps1 

   Anchor
   arguments.ps1 arguments.ps1

   in a notepad editortext editor, such as Notepad or Notepad++.
2. Enter the required information as shown in the following table.

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 parameters settings of a Configname in one of the following ways:

• Adding Entering all the parameters in the arguments cellAdding

• Entering all the parameters

  separately in different columns
  Note: 

  separately in different columns
  
  

  Info
  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.

1. Enter as configname and arguments in the cells: A1 and B1.
2. To add values for settings of a configname, do one of the following:

The following screenshot is an example of adding arguments.

Image Removed

as shown in the following screenshot:Image Added

To add all the Parameters Separately in Different Columns   Configuring the Test Cases  Step 3: Open the test-configs.csv file in any CSV supported file such as MS-Excel. Anchor Separate Separate 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. Image Removed  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: Info 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. Image Added Mapping the Configured Confignames for Test Cases For every test case, you can specify the instances.You can combine the test cases from the Suite folder and the configurations from the masterneed to map with the different Confignames. To map the configured Confignames with Test Cases: Open the test-configs.csv to execute test cases accordingly file. Enter the A1 cell as TestCase_Name.Enter all the config names from the 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 in the top row. In the first column, from A2, enter the test case name and enter Y against each Confignnames as For every test case, do the following: Enter Y against the Confignnames that you want to execute. If Enter N against the Confignames that you do not want execution on a Configname, specify as N to execute. The following screenshot shows an example of how to add parameters for each setting map confignames with test cases. Image RemovedImage Added Parallel Execution of Test cases using Windows PowerShell  Anchor ExecutionofTestcasesusingWindowsPowerShell ExecutionofTestcasesusingWindowsPowerShell Info 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/Fail) to view the step-by-step report of test case executiontotal 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 Uploading a Test case or Test Suite Execution. General Content Integrations {"serverDuration": 1381, "requestCorrelationId": "61aac17075af40d8b5e64996e976cd3c"}