The following section provides information about how to set up and execute an offline package as a part of an Azure DevOps pipeline.
The advantage of the Offline Package integration is that you can set up and configure the required Qualitia and ADO components easily and quickly. You can map an Azure DevOps pipeline with an offline suite that contains the associated test cases, which are not updated regularly.
...
The process to enable offline suite execution through Azure DevOps includes the following steps:
Process | Description |
|---|---|
Creating an Offline Package | Offline package creation is a one-time activity on your computer to execute offline suites. For detailed instructions on offline suite creation, refer to Creating an Offline Package. |
Configuring the Offline Package File | Specify in the Offline Package that the associated CI Tool is Azure DevOps. This is also a one-time activity. For detailed instructions on configuring the Offline Package file, refer to Configuring the Offline Package File. |
Creating an Offline Suite | Create a test suite that includes the test cases relevant to the pipeline. After a test suite is created, create an offline suite. For detailed instructions on offline suite creation, refer to Creating an Offline Suite. |
Mapping an Azure DevOps Pipeline with an Offline Suite | Create two tasks in the Azure DevOps pipeline and configure them to map with the Offline Package and the associated offline suite. For detailed instructions, refer to Mapping an Azure DevOps Pipeline with an Offline Suite. |
Configuring the Offline Package File
...
To configure the Offline Package file:
Open the extracted Qualitia Offline folder.
Open the config folder.
Open the startupSettings file in a text editor, such as Notepad or Notepad++.
Set the value of CI_Tool to Azure DevOps.
Mapping an Azure DevOps Pipeline with an Offline Suite
...
To map an Azure DevOps pipeline with an offline suite:
Open the pipeline in Azure DevOps.
Add
...
Command Line Prompt Utilities pipeline
...
task.
To know how to add pipeline tasks, refer to https://docs.microsoft.com/en-us/azure/devops/?view=azure-devopsOpen the
...
task and enter the following information in the Script:
Enter the location of the 64-bit Java executable path enclosed with inverted commas.
Add -jar separated by a space next to the Java path
Add Qualitia offline suite jar path enclosed within inverted commas next to -jar.
For example, "C:\Program Files\Java\jre1.8.0_261\bin\java.exe" -jar "D:\offlinesuites\Qualitia Offline\qualitiaoffline-8.3.1.jar"Optionally, you can enter the CLI Commands to override either the execution profile or specific settings of the mapped execution profile, such as browser type. For detailed instructions on how to use CLI Commands to override the settings, refer to Step 4 of Executing an Offline Suite using CLI Commands.
Expand Advanced, enter the location of the offline suite enclosed within inverted commas in the Working Directory.
For example, "D:\offlinesuites\PaymentModule\Qualitia Offline".
| Info |
|---|
Post the task execution, the following pipeline variables are available for reference in successive tasks of the pipeline:
|
Execution Guidelines and Best Practices
After mapping an Azure DevOps pipeline with an offline suite, you can now execute the mapped pipeline. To know how to execute an Azure DevOps pipeline, refer to https://docs.microsoft.com/en-us/azure/devops
...
Limitations
Whenever any test case is updated or created, you must create the associated offline suites again and also map the associated pipelines with new offline suites.
You cannot have parallel executions of test cases.
QAS does not send the suite execution results to Azure DevOps.