Ranorex Studio supports test automation for many different UI technologies. To correctly identify and interact with UI elements, Ranorex Studio may require additional access to the application under test. This process is called instrumentation.
Instrumentation helps Ranorex Studio recognize UI elements, create reliable repository items, and interact with controls during test recording and execution. The ability to identify UI elements is also called object recognition.
Depending on the application technology, instrumentation can include one or more of the following actions:
- Installing a browser extension or add-on.
- Configuring the application under test.
- Enabling remote debugging.
- Adjusting application or system settings.
- Adding code or libraries to the application.
- Using the Ranorex Instrumentation Wizard.
- Configuring a device, endpoint, or test environment.
In many cases, Ranorex Studio instruments supported technologies automatically. However, some technologies require manual setup before Ranorex Studio can recognize UI elements correctly.
How Instrumentation Relates to Plugins
Ranorex Studio uses plugins to work with specific UI technologies. For example, different plugins support WPF, Qt, SAP, CEF, browser-based applications, mobile applications, and legacy desktop technologies.
Instrumentation gives Ranorex Studio the access it needs, while plugins provide the technology-specific support for identifying and interacting with UI elements.
For example:
| Application technology | What may be required |
| Browser-based applications | Browser extension or add-on |
| CEF or Chromium-based desktop applications | Remote debugging configuration |
| SAP GUI applications | SAP GUI scripting and compatible privilege settings |
| Mobile applications | Device setup, instrumentation, and required ports |
| WPF applications | WPF plugin behavior and object recognition settings |
| Legacy desktop applications | MSAA, RawText, Delphi, or other specialized plugin support |
When Manual Instrumentation May Be Required
Manual instrumentation may be required when:
- Ranorex Spy does not recognize expected UI elements.
- The application appears as a generic window or container.
- Repository items are unstable or incomplete.
- A browser, embedded browser, or mobile device requires additional configuration.
- The application uses a specialized or legacy UI technology.
- Automatic instrumentation is not available or does not work in the current environment.
When this happens, review the setup article for the technology you are testing.
Technology-Specific Setup Articles
Use the following articles to configure or troubleshoot specific application technologies.
| Application type or scenario | Recommended article |
| You need an overview of available plugins. | Available Plugins |
| You need to understand how plugins work. | Understanding Ranorex Plugins |
| You test a Windows desktop application and need to choose between plugins. | Choosing the Right Plugins for Your Windows Application |
| You test a WPF application. | Improved WPF Plugin |
| You test a Qt application. | Qt Testing |
| You test a Delphi application. | Delphi Plugin |
| You test a SAP GUI application. | Testing of SAP Applications |
| You test a CEF, Electron, JxBrowser, NW.js, or Chromium-based desktop application. | Testing of CEF Applications |
| You test a WebView2-based application. | Inspecting WebView2-based Apps |
| You test an older desktop application. | Testing of Legacy Applications |
| You test a Flash/Flex application. | Flash/Flex Testing |