Introduction to Ranorex Integrations

Ranorex Studio integrates with tools that support different parts of your test automation workflow, including source control, continuous integration, test management, issue tracking, cloud execution, visual validation, and development environments.

Use this section to identify which integration fits your team’s workflow and where to start. Integration availability varies by Ranorex Studio version. For version-specific details, see the Ranorex Studio release notes or Supported Technologies and Versioning.

What are Ranorex integrations?

Ranorex integrations help you connect your automated tests with the tools your team already uses to build, manage, execute, and report on software testing activities.

Depending on your workflow, you can use integrations to:

• Store and version Ranorex solutions in source control.
• Run automated tests as part of a CI/CD pipeline.
• Map automated tests to test cases.
• Publish test results to test management tools.
• Connect test execution with issue-tracking and collaboration tools.
• Run tests in browser-based, remote, or cloud environments.
• Add visual validation to automated tests.
• Work with Ranorex projects in development environments.

Choose an integration based on your goal

Use the following table to find the integration section that matches your workflow.

Recommended setup path

The best integration path depends on your team’s tools and testing process. For most teams, the following order provides a practical starting point.

Start with a working Ranorex solution

Before configuring an integration, make sure that your Ranorex solution builds and runs successfully on a local machine. This helps you confirm that the test logic, object repository, test data, and execution settings are working before adding external tools to the process.

Add source control

Use source control to store and version your Ranorex solution. This allows your team to collaborate on test automation assets, review changes, and maintain a shared history of updates.

Start with Source Control and Revision Control if your team needs to work with Git, Subversion, or Team Foundation Version Control.

Use Ranorex Magic Merger to resolve merge conflicts in test files when working with any of the above version control systems. 

Configure automated execution

After your solution is under source control, configure a CI/CD integration to run tests automatically as part of your build or release process.

Start with the CI/CD tool your team already uses:

• Continuous Integration
• Azure DevOps Integration
• Jenkins Integration
• GitHub Actions Integration

Connect test management and reporting

If your team manages test cases or test runs in a test management tool, connect Ranorex test execution with that tool.

Use TestRail Integration or Azure DevOps Integration to map tests, manage test case relationships, and report results.

Add issue tracking and collaboration

If your team tracks defects or development work in Jira, use the Jira Integration to connect testing activities to issue-tracking workflows.

Add specialized integrations

After the core workflow is in place, add specialized integrations based on your application type and testing needs.

• BrowserStack Integration or Selenium WebDriver Integration for browser-based, remote, or cloud execution workflows.
• Applitools Eyes Integration for visual validation.
• Visual Studio Integration for development environment workflows.
• Flutter Integration for Flutter application testing.
• Ranorex Extensions for browser-related tools such as Ranorex Selocity and the Ranorex Chrome Extension.

Next steps

Select the integration section that matches your workflow. If you are setting up integrations for the first time, start by confirming that your Ranorex solution runs locally, adding it to source control, and configuring the CI/CD or test management integration your team uses.