Opkey integrates with Azure DevOps Services, enabling users to efficiently manage project artifacts, log bugs, map bugs with test cases, and update bug statuses within the Azure DevOps environment.
To proceed to work with it, make sure that you have registered your account on Microsoft Azure DevOps (https://azure.microsoft.com/).
Let’s see how to proceed to work with Azure DevOps Server
Login to the https://login.microsoftonline.com/ with your valid credentials.
Here are some existing projects that can be viewed on the Azure platform.
To create a new project, click "Create Project” fill in the required fields, and then click "Create" to proceed.
The project "RSP_Test" has been successfully created.
Now, go to the Opkey tool and navigate to the Tools menu on the right-hand side of Opkey, next to
the Profile menu.
Scroll down and select External Tool Integration from the options.
Check the "UseForTestManagement" box next to Azure DevOps Extension for Opkey, then click "Configure".
Now enter your Azure DevOps credentials and click on the Login button.
Note - Enter the API token as the password.
Select your project, check the "Linked to Opkey Project" checkbox, and click "Configure".
Click on the '+' to Add a workflow.
Configure your workflow by selecting desired values from the dropdown menus, then click "Save".
To map a Test Case with the Test plan and Bugs of Azure DevOps, right-click on the Test Case, then select "Azure DevOps Mapping".
The Azure DevOps filter will appear. Select the required filter fields, then click on "Search"
Here is the test plan existing in the selected project. Let's map it with the test case so that it can be updated according to the test case execution status.
Select the test plan and click on Apply Mapping Changes.
Once the mapping is completed, a message "All mappings successfully saved" will be displayed.
After this, you can execute these test cases in Opkey. Once the test execution is completed, you can review the test results. Any bug or defect related to the executed test case will be logged into your Azure environment. Review the updated test plans and the newly logged bugs.
Review the details of the newly logged bug to understand the reason for the test case failure.
View the Execution Stats to analyze the overall execution performance and status of the test cases.
You can access the execution attachment link here to view additional details or documents related to the test execution.
You can download attachments from this section by clicking on the links provided.
Executing Opkey Suites on Azure DevOps
After integration, Opkey enables direct execution of your test suites within the Azure DevOps environment.
To execute test cases in pipelines, you need to install additional Opkey extensions.
To do so, type Opkey in the search bar.
The image below shows three Opkey Extensions: Opkey Test, Opkey CI, and Opkey Execution Stats. Install all three extensions one by one.
Here are the steps to execute a test suite of Opkey within the Azure DevOps environment:
Log in to the Microsoft Azure DevOps platform using your valid credentials.
Navigate to the Pipelines tab from the left pane of the dashboard.
Click on the Pipeline option.
Select an existing pipeline or create a new one by clicking "New Pipeline".
This view is of Azure Classic. Here, select your Git account or choose the "Other Git" option to add a general account for storing data.
In the Other Git option, by default a master branch will be created. Click Continue to proceed with the master branch.
Click the Empty Job option in the next window.
Select the “Get Sources” option on the next window and check the checkbox of “Don’t Sync sources”. This will sync the existing data. If it remains unselected, the executions will fail.
Next, navigate to the "Agent" section and click the "+" button to add a new agent.
Search for the Opkey plugin on the Azure platform to add. In the search box, type "Suite" and then click the "Add" button.
Select the plugin and check the corresponding checkbox. Click the "New" button in the next column to add a new connection.
In the window that opens, enter the details for the Service URL, Username, and Password, then click "Verify." A confirmation message will appear once the verification is successful. Next, provide the Service connection name, add a description, and select the "Grant access permission to all pipelines" checkbox. Finally, click "Verify" and "Save."
Once the connection is created, it will appear in the dropdown. Search for it and select to add it.
Select the Project, Suite Path, Build, Session Name, and Agent.
Select the Plugin, Snapshot Quality, Report Type, and Step Timeout.
Select the "Update mapped Test Management artifact" checkbox to log bugs for failed executions. Then, select the "Wait for Execution Result" checkbox to pause until the execution result is available. Finally, click "Save and Queue."
Provide the name and click on Save and Run.
The execution will be queued.
It will pause for a moment before starting the execution. Once the agent becomes available, the execution will commence.
You're at the end of the article.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article