Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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:

...

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

...

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.