Microsoft Azure DevOps is a set of services for planning work, collaborating on code, and running CI/CD pipelines. It’s available as Azure DevOps Services (cloud) and Azure DevOps Server (on-premises). Review https://azure.microsoft.com/en-us/ for more information.
In this section, you’ll learn how to use the Ranorex Studio Azure DevOps integration to run automated Ranorex tests as part of an Azure Pipelines build pipeline.
How the integration works
The integration relies on multiple systems working together, as shown in the diagram below:
- Your Ranorex Studio solution is stored in a Git repository (the repository folder) and is under Git version control.
- Your Azure DevOps project connects to that repository via Azure Repos and uses Git for version control.
- Your Azure DevOps project includes one or more pipelines that provide CI functionality for building and executing the Ranorex Studio solution.
- The pipeline runs on one or more Azure Pipelines agents, where the tests are executed.
Software requirements
To use the Azure DevOps integration, you need the following software:
Ranorex Studio
To create and maintain tests, you need Ranorex Studio installed with a license that supports test authoring. To execute tests on agent machines, you may need a license intended for test execution/runtime, depending on your licensing model and setup. For details about available license models, see Pricing.
Azure DevOps account
You need an Azure DevOps organization/project. Azure DevOps offers free and paid plans depending on features and usage (including Test Plans and parallel job needs). For more information about features and pricing, see the Azure DevOps product page.
Git
The integration uses Git for version control and to provide the Ranorex Studio solution to the Azure DevOps project. Git is available under the GNU GPL (v2). You can download it from git-scm.com.
Microsoft Visual Studio
Azure Pipelines builds Ranorex Studio solutions using Microsoft build tools. Install Microsoft Visual Studio (or Visual Studio Build Tools) on any machine that will build the solution as part of the pipeline. For details about available versions, visit visualstudio.microsoft.com.