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.
...
Hence, Qualitia also supports the Azure DevOps Advanced integration that solves all the above mentioned problems. For detailed instructions, refer to Azure DevOps Advanced Integration.
Pre-Requisites
Ensure that your computer:
...
Whenever the test cases of the corresponding test suite are updated in QAS, perform the following steps:
Create the offline suite again.
Save the new offline suite in another location of your computer.
Open the Azure DevOps pipeline to replace the mapped offline suite.
To allow the suite execution results to display in the Real Time Reporting portal, ensure that you specify the Qualitia Server URL and select the Real Time Reporting checkbox in the mapped execution profile.
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.
To 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.
You can edit the test data for an offline suite and execute the pipeline again 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.
...
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.