Azure Pipelines let you build, test, and publish artifacts from your repository. You can use Azure DevOps pipelines to build a Ranorex Studio solution and run the resulting test executable on a configured Azure Pipelines agent.
Ranorex Studio tests require a Windows agent with an interactive desktop session. Before you create a pipeline, make sure your agent is installed, configured, online, and ready to run UI tests.
Choose a Pipeline Type
Azure DevOps supports two pipeline types:
| Pipeline type | Description | Recommended for |
| YAML pipeline | Defines the pipeline in a .yaml or .yml file stored in your repository. | New pipeline setups, version-controlled configuration, and repeatable CI/CD workflows. |
| Classic pipeline | Defines the pipeline through the Azure DevOps web interface. | Existing classic workflows or users who prefer configuring tasks through the UI. |
Recommended Approach
For new Azure DevOps pipeline setups, use a YAML pipeline. YAML pipelines keep the pipeline configuration in your repository, so changes can be reviewed, versioned, and reused across environments.
Use the classic editor if your organization already uses classic pipelines or if you need to follow an existing classic pipeline setup.
Note: Some Azure DevOps organizations disable the creation of new classic pipelines. If you don’t see the classic editor option, use a YAML pipeline or ask your Azure DevOps administrator to review the organization pipeline settings.
Before You Begin
Make sure you have:
- An Azure DevOps project and Git repository. See Create ADO Project and Git Repo.
- A configured Azure Pipelines agent. See Set Up an Azure Pipelines Agent.
- A Ranorex Studio solution committed and pushed to your Azure Repo.
- Access to create pipelines in your Azure DevOps project.
- Read access to the repository that contains your Ranorex Studio solution.
Next Steps
Choose the setup that matches your workflow: