...
Prerequisites for Azure DevOps
Azure DevOps Version |
|
Qualitia Plugins | Share Azure DevOps URL to Qualitia team to get the Get Assembly task plugin. |
Roles and Privileges |
Note: Please connect with your Azure DevOps Admin team to discuss the PAT generation and access level management. Qualitia integration with Azure DevOps expects that the user has “Update Work Items” access that is used to generate the PAT (Personal Access Token). The PAT with required access can be procured in one of the following ways:
|
Prerequisites for Qualitia
Roles and Privileges |
|
Network Access |
|
Configuring Azure DevOps for Test Executions
QAS provisions to To execute automated test cases from QAS Qualitia mapped to Azure DevOps , as a part of your build and release pipelines. In order to do so, you first need to add the Qualitia - Test Execution extensions in to your Azure DevOps instance. Follow the steps to add these extensions in these steps:
Share Azure DevOps Organization Details:
...
Before
...
integrating Azure DevOps
...
with Qualitia,
...
provide your Azure DevOps organization details
...
to Qualitia.
...
They will then share the
...
necessary extensions for integration with your Azure DevOps projects
...
.
...
Add and Install Extensions: Once Qualitia shares
...
the extensions, you can add and install
...
them in
...
your Azure DevOps instance
...
.
Installation Steps:
Sign
...
into Azure DevOps instance.
...
Click the top-right corner
...
to navigate to Marketplace > Manage Extensions.
...
Locate the Qualitia - Test Execution extension shared by Qualitia.
Click the Qualitia - Test Execution and install it.
...
Verify Installation: Return to Extensions > Manage Extensions to confirm that the installation was successful.
Your Azure DevOps instance is now configured for Qualitia integration and ready to use in build and release pipelines.
Configure Qualitia - Test Execution Task
Add Task in CI-CD Pipeline
Log into Azure DevOps instance.
Add new CI-CD pipeline or edit the existing pipeline.
To create new pipeline, select required repository or use the Select classic view option.Click the + icon to add new task.
Search and select Qualitia - Test Execution and add it.
After you add the custom task into the CI-CD pipeline, you must configure it by adding the following details:
Display Name | Enter the desired display name for this task. |
Qualitia Option | |
Enter Qualitia Server URL | Enter the hostname or IP of the machine where QAS server is installed and enter server port number, by default it will use port 8887.
|
Enter Qualitia Project Name | Name of QAS project that is integrated with Azure DevOps. |
Execution Parameter | Specify QAS execution parameter such as non-default browser to use will execution and override environment variable. By default, None is selected. |
Test Selection | |
Test Plan | Select a test plan containing test suite with QAS automated test cases. |
Test Suite | Select test suite containing QAS automated test cases. You can select more than one suite here. |
Execution Option | |
Distribution mode | Batch test across agents: Distribute test case across agent in define number of tests per batch. Replicate all tests across all agents: Execute all test cases on all agent configured. |
Control Option | |
Enabled | This shows the current state of the customized task, and gives you control over the customized task. By default, this option is selected. Clear this option to disable a task. It is useful when you want to temporarily take task out of the process for testing or for specific deployments. |
Continue on error | Select this option if you want to continue QAS test case execution even after getting errors in the pipeline. By default, this option is not enabled. |
Timeout | Set the timeout for the task in minutes. Default is 0, which refers to infinite timeout. Value set here overrides the value set for the parent task job. |
Run this task | Here you can set the condition to run a task. You can use one of the pre-designed options in the list or you can create new customized condition. You may refer to Azure DevOps documentation for more information on creating custom conditions as expressions. |
...
You need to enable Allow scripts to access the OAuth token from Agent job.
...
Connecting Qualitia Artifacts to Azure DevOps
After you set up the environment in Azure DevOps for automating tests using Qualitia, it is now time to map your Qualitia artifacts to Azure DevOps where its starts with mapping a Qualitia project to Azure DevOps project.
Qualitia Test Case Lifecycle for Azure DevOps Integration
During the integration process with Azure DevOps, the Qualitia test case progresses through various stages, impacting the status of the associated Azure DevOps manual test case. Below is a description of each stage and its implications:
The following diagram shows the Integration Lifecycle status for a test case.
...
The following sections explain the different stages of a Qualitia test case and the impact of the same on associated Azure DevOps manual test case.
Test Case Creation
When a new test case is created in Qualitia under an Azure DevOps-integrated project, it remains unassociated with any Azure DevOps manual test case. The status of the Qualitia test case is marked as Not Linked.
Test Case Linking with Azure DevOps Test Case
The association between Qualitia test case and Azure DevOps test case is established on linking a test case with Azure DevOps test case. Refer to the following link for more details on how to link a test case with Azure DevOps manual test case.
Qualitia Test Case Status Change:
Not Linked → Linked/Not PublishedAzure DevOps Test Case Automation Status Change:
Not Automated → Planned
Publishing Test Case
Once the Automation Engineer completes the test case in Qualitia and is ready for execution in Azure DevOps, the test case must be published.
Qualitia Test Case Status Change:
Linked/Not Published → Linked/PublishedAzure DevOps Test Case Automation Status Change:
Planned → Automated
Editing a Test Case after Publishing
If changes are made to the Qualitia test case after publishing, these changes do not reflect in Azure DevOps. The published version is used for test execution.
Qualitia Test Case Status Change:
Linked/Published → Linked/Changes Not PublishedAzure DevOps Test Case Automation Status:
Automated → Automated
Test Case Unlinking with Azure DevOps Test Case
The link between the Qualitia test case and the Azure DevOps test case can be removed at any time by unlinking the test case.
Qualitia Test Case Status Change:
Linked/Published or Changes Not Published → Not LinkedAzure DevOps Test Case Automation Status Change:
Automated → Not Automated
Linking a QAS Project to an Azure DevOps Project
To link a Qualitia project to an Azure DevOps project:
Log into Qualitia as a project administrator.
From the Expand Menu, click Project Management.
In the left pane, click a project that you want to link.
In the main pane, next to Integrations (ADO), click on link icon.
In the Azure DevOps tab, enter the following details of Azure DevOps.
Server URL: Enter the Azure DevOps URL.
PAT Token: Enter Personal Access Token (PAT) for authentication.
Connect: Click to connect to Azure DevOps server.
Azure DevOps Project: Select an Azure DevOps project from the drop-down list. User can select multiple projects.
Click Integrate.
Linking a Qualitia Test Case to an Azure DevOps Test
You can link a test case either from the Test Case Editor screen or from Ready for Execution screen.
To link a test case from the Test Case Editor screen:
From the Expand Menu, click Develop.
From the left pane, select a scenario, and open the test case.
Click the Link button
To link a test case from the Ready for Execution screen:
From the Expand Menu, click Execute.
Click the Ready for Execution tab.
A list of test cases is displayed in Test Case tab
Update the following details The below screen will open in both the cases:
🔧 Got a problem? Let’s fix!
...