Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
You can execute Azure DevOps pipelines by mapping them with the relevant offline suites.
Pre-requisites:
Ensure that your computer contains the following components:
Access to Azure DevOps
- Contains the Azure DevOps self-hosted agent.
- Satisfies all the pre-requisites for offline suite execution. For more details, refer to Prerequisites for Offline Suite Execution.
Setting the Qualitia and Azure DevOps Components
Enabling your computer to execute an offline suite through Azure DevOps includes the following process:
| Creating a Build or Release Pipeline | Create a build or a release pipeline to map with Qualitia test cases. For detailed instructions, refer to the following links: |
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. Note: If you have installed the QAS client on another computer, |
create the offline package from that computer and transfer it to your computer. | |
| Configuring the Offline Package File | Specifying in the Offline Package that the associated CI Tool is Azure DevOps. This is also a one-time activity. For detailed instructions on offline suite creation, refer to Creating an Offline Suite. |
| 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 jobs 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. |
| Executing the Pipeline | You can go ahead to execute the Azure DevOps pipeline after configuring its jobs. To know how to execute an Azure DevOps pipeline, refer to https://docs.microsoft.com/en-us/azure/devops/?view=azure-devops |
Configuring the Offline Package File
| Info |
|---|
You can skip this configuration if you set the value of CI_Tool to Azure DevOps in the mapped execution profile of the offline suite that you want to execute. |
To configure the Offline Package file:
- Open the extracted Qualitia Offline folder.
- Open the config folder.
- Open the startupSettings file in Notepad.
- Set value of CI_Tool to Azure DevOps.
Mapping an Azure DevOps Pipeline with an Offline Suite
After creating a build or a release pipeline, map it with the corresponding offline suite. In the Azure DevOps
.Configuring the Pipeline
To configure the pipelinepipeline, create two jobs that are used to:
- Invoke the Offline Package and the mapped offline suite as per their specified locations.
- Get the total number of test cases executed and the number of test cases executed for each execution status.
To map an Azure DevOps pipeline with an offline suite:
- Open the pipeline in Azure DevOps.
- Add two Command Line Prompt Utilities with names of your choice.
Azure DevOps adds these two as jobs.
To know how to add pipeline jobs, refer https://docs.microsoft.com/en-us/azure/devops/?view=azure-devops - Open the first job to enter the following information, in Script:
- Enter the location of the Java path enclosed with inverted commas.
- Add -jar separated by space next to Java path
- Add Qualitia offline suite jar path enclosed with inverted commas next to -jar.
For example, "C:\Program Files\Java\jre1.8.0_261\bin\java.exe" -jar "D:\offliesuites\Qualitia Offline\qualitiaoffline-8.3.1.jar"
- Expand Advanced, enter the location of offline suite enclosed with inverted commas, in Working Directory.
For example, "D:\offliesuites\PaymentModule\Qualitia Offline". - Open the second job to enter the following information, in Script:
@echo PassedCount = %PASSEDCOUNT%
@echo FailedCount = %FAILEDCOUNT%
@echo DefectCount = %DEFECTCOUNT%
@echo NotExecutionCount = %NECOUNT%
@echo TotalCount = %TOTALTCCOUNT%
Note: You can specify the names of jobs, such as Qualitia Offline Suite Name and Suite Name Settings to identify the pipeline with the offline suite.
Executing a Pipeline
After you configure the jobs of the pipeline in Azure DevOps, execute the pipeline in Azure DevOps.- .
You can now execute the Azure DevOps pipeline.
Best Practices for Azure DevOps Pipeline Execution with Offline Package
Qualitia recommends considering the following best practices to optimize the Azure DevOps pipeline executions that are mapped with offline suites:
- Before executing a pipeline, ensure that the mapped execution profile of the corresponding offline suite is configured as per the requirements. For detailed instructions, refer to Configuring the Settings for an Offline Suite.
- You can execute a pipeline on different browsers, environments and other execution settings. Create different execution profiles in the QAS client and export them into the Offline Suite folder of your computer. For detailed information on execution profile, refer to Working with Execution Profiles.
- Whenever a test case relevant to a pipeline is updated in the QAS client, perform the following steps:
- Create the offline suite again using the corresponding test suite.
- Save the offline suite in another location of your computer.
- Open the Azure DevOps pipeline to replace the mapped offline suite.
- You can edit the test data for an offline suite to cover more test scenarios. For detailed instructions on editing test data for an offline suite, refer to Editing the Test Data for an Offline Suite.
Viewing the Suite Execution Reports
If you have configured the Qulaitia Server URL in the mapped execution profile, you can track the pipeline execution in the Real Time Reporting Portal.
The suite execution result is displayed as Offline Azure DevOps.
ElseHowever, if you did not connect with Qulaitia Qualitia Server or the connection with Qualitia Server was lost during the pipeline execution. , you can upload the locally saved suite execution report in the following ways:
- Uploading a Test Suite Execution Summary Report
- Uploading Multiple Suite Execution Reports to Real-Time Reporting Portal
On this page:
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|