Ranorex Studio uses plugins to identify, access, and interact with UI elements in different application technologies. Each plugin provides support for a specific framework, platform, browser, or automation interface.
Plugins work in the background when you record, track, inspect, or execute tests. In most cases, Ranorex Studio selects the required plugin automatically based on the application under test. However, some technologies require additional setup before Ranorex Studio can correctly identify UI elements.
Use this article to understand how Ranorex plugins work, when additional configuration is required, and where to find setup or troubleshooting information for specific technologies.
What Is a Ranorex Plugin?
A Ranorex plugin is a technology-specific component that helps Ranorex Studio recognize and interact with UI elements.
Plugins help Ranorex Studio work with different application types, including:
- Desktop applications
- Web applications
- Mobile applications
- SAP applications
- Java applications
- Qt applications
- WPF and Windows Forms applications
- WebDriver endpoints and Selenium grids
- Data-driven testing sources
Each plugin exposes supported UI elements to Ranorex Studio so you can track, identify, validate, and automate them.
How Ranorex Studio Uses Plugins
Ranorex Studio uses plugins when you:
- Track UI elements with Ranorex Spy.
- Record user actions.
- Create repository items.
- Execute automated tests.
- Validate UI elements.
- Interact with technology-specific controls.
When Ranorex Studio inspects an application, it evaluates the available UI technologies and uses the plugin that matches the detected element type.
For example:
| Application or technology | Plugin usually involved |
| Google Chrome web application | ChromeWeb |
| Mozilla Firefox web application | Firefox Web |
| CEF or Chromium-based desktop application | CEF |
| WPF desktop application | WPF or WPF.Core |
| Windows Forms desktop application | WinForms or WinForms.Core |
| Java application | Java |
| Qt application | Qt |
| SAP GUI application | SAP |
| Android or iOS application | Mobile |
| Selenium Grid or WebDriver endpoint | WebDriver |
Plugin Categories
Ranorex plugins support different parts of the test automation workflow.
| Category | Description | Examples |
| Browser plugins | Support DOM-based web automation in supported browsers. | ChromeWeb, Firefox Web, Web |
| Desktop technology plugins | Support desktop UI frameworks and Windows automation interfaces. | WPF, WPF.Core, WinForms, WinForms.Core, Qt, Java, Delphi, UIA, MSAA, Win32 |
| Embedded browser plugins | Support embedded Chromium-based application content. | CEF |
| Mobile plugins | Support Android and iOS device testing. | Mobile, Mobile.Android.Remote, Mobile.iOS.Remote |
| Enterprise application plugins | Support specialized business application platforms. | SAP |
| Remote execution plugins | Support execution through WebDriver endpoints or grids. | WebDriver, WebDriver.Remote |
| Data connector plugins | Support external data sources for data-driven testing. | ExcelDataConnector |
| Specialized recognition plugins | Support fallback or specialized recognition scenarios. | RawText, Office |