Skip to main content
QASkills.sh
Sign In
Back to Blog
Guide
2026-05-03

Ranorex Test Automation Complete Guide 2026

Master Ranorex Studio for desktop, web, and mobile test automation in 2026. Object identification, recording, code modules, CI integration, and Ranorex DesignWise.

Ranorex Test Automation Complete Guide 2026

Ranorex Studio is a Windows-based GUI test automation platform from Idera (owners of Embarcadero and others). The product specializes in desktop application testing where Selenium and Playwright do not reach: Win32, WPF, Java SWT, Delphi, and other native desktop technologies. It also covers web and mobile through its integrated platform. For teams that test desktop applications alongside web, Ranorex is one of the few unified options.

This guide covers Ranorex Studio end to end: installation, object identification with RanoreXPath, recording, code modules in C#/VB.NET, mobile testing, web testing, Ranorex DesignWise for combinatorial test generation, and CI/CD integration. We include screenshots described, sample tests, and a setup checklist. By the end you should understand whether Ranorex fits your team and how to roll it out. The guide assumes basic .NET familiarity but record-and-play features work without coding.

Key Takeaways

  • Ranorex is a Windows-based GUI test automation platform; specialized in desktop apps but covers web and mobile.
  • RanoreXPath is Ranorex's locator system: a powerful XPath variant for any GUI technology.
  • Tests authored via Recorder, organized as test cases, organized as test suites.
  • Code modules in C#/VB.NET handle complex logic.
  • DesignWise generates combinatorial test cases from input parameters.
  • For teams with desktop testing needs, Ranorex is a strong choice; for web-only, lighter tools are better.

Why Ranorex

Ranorex's value proposition is desktop automation. Most test automation tools focus on web and mobile; Ranorex covers desktop with the same first-class support.

The supported technologies include:

Win32 native applications.

WPF (Windows Presentation Foundation).

WinForms.

Java SWT, AWT, Swing.

Delphi.

Microsoft Office.

Citrix and Remote Desktop.

For teams shipping desktop products, Ranorex is one of the few unified options.

The trade-offs: Windows-only (no Linux or macOS for the Studio), expensive per-seat licensing, and steeper learning curve than newer SaaS tools.

Installation

Download Ranorex Studio from ranorex.com. The installer runs on Windows 10/11.

Ranorex Studio
Version: 11.x
Platforms: Windows 10/11 (64-bit)

Install with the platform installer. License activation requires an Idera account.

For team setups, install Ranorex on each developer's machine plus dedicated agent machines for distributed execution.

Project Structure

A Ranorex Studio solution has standard structure.

MySolution/
  MyProject/
    Test Cases/
      Login.rxtst
      Checkout.rxtst
    Recordings/
      LoginRecording.rxrec
    Repository.rxrep
    UserCode/
      LoginHelpers.cs

The repository stores object locators. Recordings capture actions. User code adds custom logic.

Object Identification with RanoreXPath

RanoreXPath is Ranorex's locator system. A locator targets a GUI element via its properties.

//form[@title='Sign In']/button[@text='Submit']

The syntax mirrors XPath but uses Ranorex's GUI element types (form, button, edit, list, tree, etc.) and properties (title, text, accessibleName, etc.).

For complex applications, RanoreXPath is more expressive than CSS selectors or simple XPath.

// Find a tree item by partial text
/tree/item[contains(@text, 'Settings')]

// Find a row in a grid by cell content
/grid/row[cell[@text='Alice Smith']]

// Find a button by relative position
/form[@title='Login']/button[3]

Object repositories store these locators with friendly names. Tests reference repository items, not raw locators.

Recording Tests

The Recorder captures actions in any GUI application.

1. Open Ranorex Studio
2. New > Recording
3. Set start application or URL
4. Perform actions
5. Add validations via the Recorder toolbar
6. Stop and save

The recording is a sequence of actions: click, type, validate, wait. Each action references a repository element.

<RecordItem name="Type 'alice@example.com' on Email input">
  <Action type="Key Sequence">
    <RepoItem ref="EmailInput" />
    <Value>alice@example.com</Value>
  </Action>
</RecordItem>

The recording is editable. Add steps, change parameters, organize into groups.

Test Cases and Suites

Test cases are sequences of recordings and code modules.

Test Case: Login with valid credentials
  Step 1: Setup recording (start app)
  Step 2: Login recording (type credentials, click submit)
  Step 3: Validation recording (assert welcome message)
  Step 4: Teardown recording (close app)

Test suites group test cases with parameters, data sources, and execution order.

<TestSuite>
  <TestContainer name="Smoke Tests">
    <TestCase ref="Login" />
    <TestCase ref="Checkout" />
  </TestContainer>
</TestSuite>

Run a test suite via the IDE or CLI.

Code Modules

For complex logic, write code modules in C# or VB.NET.

[TestModule("Login", "Logs in as a specific user")]
public class LoginModule : ITestModule
{
    [TestVariable]
    public string Email { get; set; }

    [TestVariable]
    public string Password { get; set; }

    void ITestModule.Run()
    {
        var repo = MyRepository.Instance;
        repo.LoginForm.EmailInput.PressKeys(Email);
        repo.LoginForm.PasswordInput.PressKeys(Password);
        repo.LoginForm.SubmitButton.Click();
    }
}

Code modules integrate with recordings. A test case can mix recorded steps and code module calls.

For teams comfortable with .NET, code modules are the path to maximum control.

Data-Driven Testing

Data-driven testing in Ranorex uses CSV, Excel, or SQL data sources.

Email,Password,Expected
alice@example.com,secret123,Welcome Alice
bob@example.com,letmein,Welcome Bob

Bind the CSV to test variables; the test runs once per row.

<TestCase>
  <DataSource ref="LoginUsers" />
  <Iteration>
    <RecordingModule ref="LoginRecording" />
  </Iteration>
</TestCase>

This is the standard pattern for testing many user variations efficiently.

Mobile Testing

Ranorex supports iOS and Android via Appium.

Project: Mobile App Tests
  Device: iPhone 14 (Simulator)
  Device: Pixel 7 (Emulator)

Mobile recording captures taps, swipes, and assertions. RanoreXPath identifies mobile elements via accessibility attributes.

For mobile-heavy teams, dedicated mobile tools (Mabl, Functionize) may be better. For teams that test both desktop and mobile, Ranorex covers both.

Web Testing

Ranorex's web testing uses Selenium-style locators plus RanoreXPath.

//web/form/input[@type='email']
//web/form/button[@text='Submit']

The web engine supports Chrome, Firefox, Edge, and Safari.

For pure web testing, Playwright or Cypress are typically better choices. Ranorex web is useful when you need web + desktop in one tool.

Ranorex DesignWise

DesignWise is a separate product for combinatorial test generation. Given input parameters, DesignWise generates an optimized test set.

Parameters:
  Browser: Chrome, Firefox, Safari, Edge
  Device: Desktop, Tablet, Mobile
  Language: English, Spanish, German, French
  User Type: Guest, Member, Admin

Combinations: 4 * 3 * 4 * 3 = 144
Pairwise reduced: 12 test cases

DesignWise uses pairwise testing to cover all parameter pairs with minimal tests. For complex inputs, this dramatically reduces test count while maintaining coverage.

CI/CD Integration

Ranorex integrates with Jenkins, Azure DevOps, GitHub Actions, and other CI tools.

// Jenkinsfile
pipeline {
  agent { label 'ranorex-agent' }
  stages {
    stage('Tests') {
      steps {
        bat 'TestSuite.exe /runconfig:Smoke /reportfile:report.rxlog.xml'
        archiveArtifacts artifacts: 'report.*'
      }
    }
  }
}

The compiled test suite is a Windows executable; the CI agent runs it. Reports include screenshots and execution traces.

Reporting

Ranorex generates HTML reports with screenshots, durations, and error context.

Test Suite Report
  Duration: 15m 22s
  Test cases passed: 23 / 25
  Failed:
    - Login_InvalidPassword: Element not found at step 5
    - Checkout_OutOfStock: Validation failed at step 12

For failed tests, the report includes screenshots at failure and a trace of preceding steps. Useful for diagnosing intermittent failures.

Pricing

Ranorex pricing is per-seat, with floating and node-locked licenses.

Ranorex Studio: ~$3,500 per node-locked license
Floating license: ~$5,000 per concurrent user
Ranorex DesignWise: ~$5,000 per user

For a 10-person team, expect $35k-$60k per year in licensing.

The pricing is mid-range: more than Katalon but less than Tosca.

Comparison to Alternatives

ToolDesktopWebMobilePricing
RanorexBest-in-classGoodYes (Appium)Mid
ToscaBest-in-classGoodYesHigh
TestCompleteGoodGoodYesMid
SquishBest for QtGoodYesMid
SeleniumNoBestNoFree

For desktop testing, Ranorex, Tosca, TestComplete, and Squish are the main options. Ranorex is mid-priced and covers the broadest desktop technology range.

When to Choose Ranorex

Choose Ranorex if:

You test desktop applications (Win32, WPF, Java, Delphi).

You need one tool for desktop + web + mobile.

Your team is comfortable with .NET.

You operate on Windows.

Avoid Ranorex if:

Your testing is purely web/mobile.

You need cross-platform (Linux/Mac) tooling.

Budget is constrained.

Setup Checklist

License and install Ranorex Studio.

Create a project for your application.

Author a first recording.

Set up the repository with key elements.

Write a code module for reusable logic.

Configure data sources for data-driven tests.

Build a test suite combining recordings and code modules.

Configure CI/CD with the compiled test suite.

Set up reporting and archive policy.

Train the team on RanoreXPath and code modules.

Common Patterns

Pattern 1: hybrid recording + code. Record happy paths, code edge cases.

Pattern 2: repository-driven design. Centralize all locators in the repository. Tests reference repository entries, not raw locators.

Pattern 3: data-driven validations. One test, many input combinations from CSV.

Pattern 4: DesignWise for complex configurations. When parameters explode, use DesignWise to reduce.

Common Pitfalls

Hardcoded locators. Use the repository; do not embed locators in code.

Brittle absolute paths. Use partial matches and attributes; avoid relying on element index.

No data strategy. Hardcoded test data ages poorly. Use data sources from day one.

Skipping code modules. Without code modules, tests duplicate logic.

Inadequate CI integration. Run tests in CI from the first test, not after the suite is large.

Migration

From Selenium: Ranorex web testing differs in object identification. Rewrite locators in RanoreXPath; plan 1-2 weeks per 100 tests.

From UFT: UFT migration is more straightforward because the paradigms are similar (Windows GUI testing). Plan 3-6 months for a large suite.

From TestComplete: Both are Windows-focused. Migration is feasible but requires rewriting in Ranorex's format.

Further Resources

  • Ranorex documentation at ranorex.com/docs.
  • Compare desktop testing tools at /blog.
  • Browse desktop testing skills at /skills.

Conclusion

Ranorex Studio is the leading desktop test automation platform that also covers web and mobile in one tool. RanoreXPath is more expressive than typical locators; the .NET-based code modules give power users full control. For teams testing desktop applications, Ranorex is a strong choice. Browse /skills for related tools and the /blog for deeper comparisons.

Ranorex Test Automation Complete Guide 2026 | QASkills.sh