1. Home
  2. Opkey Help
  3. 22. External Tool Integration with Opkey Web
  4. 22.1 Working with Azure DevOps

22.1 Working with Azure DevOps


OpKey now supports Azure DevOps Services and Azure DevOps Server. As Microsoft has changed Visual Studio Team Services as Azure DevOps Services and Team Foundation Server as Azure DevOps Server so we have also changed our backend APIs and mechanism to support Azure DevOps Services as well as Azure DevOps Server with OpKey. Visual Studio Team Services and Team Foundation Server were already supported by the OpKey. You can now configure Azure DevOps Services with OpKey and work on it. By using Azure, you can map your project artifacts to log new bugs, map bugs with the test case, update status of logged bugs and do more.

Make sure that you have registered your account on Microsoft Azure DevOps (https://azure.microsoft.com/).


Working With Azure DevOps Server

  • Let us create a new project.
  • Click on Create Project. Fill all required fields and click on Create.

  • A New Project (named as RSP_Test) has been created successfully.

  • Now, you need to install OpKey Azure DevOps Extensions. Navigate to the Manage extensions, as shown below. Click on Browse Marketplace.

  • Type OpKey in the search bar.
  • Here are three OpKey Extensions as OpKey Test, OpKey CI, and OpKey Execution Stats.
  • Install all three extensions one by one.

  • Click on External Tool Integration under Tools menu.

  • Here, you can have a look at the existing external tools supported by the OpKey.
  • Check UseForTestManagement checkbox corresponding to the Azure DevOps Extension for OpKey and click on the Configure button.

  • Select your Project, check Linked To OpKey Project checkbox and click on the Configure button.

  • From here, you can configure your workflow.
  • Select desired values from dropdown and click on Save.

  • Let us map a Test Case with the Test plan and Bugs of Azure DevOps.
  • Right click on the Test Case and then click on Azure DevOps Mapping.

  • Azure DevOps filter appears.
  • Select required filter fields and click on Search.
  • Here are two test plans existing in the selected project. Let us map them with the test case so that they can be updated as per the test case execution status.
  • Select both Test Plans and click on Apply Mapping Changes.

  • A message “All Mappings Successfully Saved” appears.
  • Click OK.

  • Execute the mapped Test Case.
  • Make sure that “Update Mapped Test Management Artifact” checkbox is checked from Advanced execution settings.

  • Have a look at the execution logs. The test case gets failed.
  • Mapped Test Plans have been updated whereas a new bug has been logged.

  • Have a look at the updated Test Plans and new bug logged.

  • Have a look at the details of the new bug logged on test case failure.

  • You can look at the Execution Stats here.

  • Here, you can have a look at the execution attachment link.

  • From here, you can download attachments.

Executing OpKey Suites on Azure DevOps

Azure DevOps, integrated with OpKey, now allows you to execute your Suites directly from the Azure DevOps environment.

Let us see how to execute a Suite of OpKey from Azure DevOps environment.

  • Login to the Microsoft Azure DevOps (https://dev.azure.com/) with your valid credentials.
  • Navigate to the Pipelines tab from left pane.
  • Click on New Build pipeline under New to create a new pipeline.

  • Select Test as Repository, master as Default branch for manual and scheduled builds and click on Continue.

  • From here, click on Empty job as a template to proceed.

  • Configure your job from here.

  • Click on Save & queue under Save & queue.

  • Save your build pipeline and queue.
  • Click on Save & queue to proceed.

  • Build #86 has now been queued.
  • Click on the #86 link to view execution details.

  • Here, you can have a look at the build details.
  • The build has executed successfully.

Was this article helpful to you? Yes No