Use this article if Ranorex displays a Technology Limitation warning when tracking or automating an application.
A Technology Limitation warning indicates that Ranorex cannot access the application with the technology-specific capabilities normally available for that application type.
Symptoms
You may experience one or more of the following:
- Ranorex Spy displays a Technology Limitation warning.
- Ranorex Spy identifies only basic or native elements instead of the expected application controls.
- Web, CEF, Java, or other technology-specific elements cannot be recognized.
- Repository paths contain less detailed information than expected.
- Recording or replaying actions against application controls does not work correctly.
Cause
Technology Limitation warnings are commonly caused by incomplete or incorrect instrumentation.
Ranorex uses technology-specific plugins and instrumentation to access information that is not available through standard operating-system interfaces.
If the required instrumentation is missing, Ranorex may only have limited access to the application's UI.
Other possible causes include:
- The application was started before instrumentation was applied.
- A browser or application version is not supported.
- The required Ranorex plugin is disabled.
- The application architecture or configuration prevents instrumentation.
- Ranorex Studio and the application under test are running with different privilege levels.
- A browser extension or application-specific component required for automation is missing.
Diagnose the issue
Identify the application technology
First, determine which technology the application uses.
Examples include:
- Web
- Chromium Embedded Framework (CEF)
- Java
- WPF
- WinForms
- SAP
- Mobile
The required instrumentation steps depend on the application's technology.
Check instrumentation
Verify that the application has been instrumented according to the instructions for its technology.
If you recently:
- Updated Ranorex Studio.
- Updated the application.
- Updated a browser.
- Changed the application executable.
- Changed the deployment environment.
Repeat the applicable instrumentation procedure before testing again.
Check privilege levels
Run Ranorex Studio and the application under test with the same Windows privilege level.
For example, if the application runs as administrator, start Ranorex Studio as administrator as well.
Then try tracking the application again.
Check the Ranorex plugins
- In Ranorex Studio, open Tools > Options.
- Review the plugin settings.
- Verify that the plugin required for the application's technology is enabled.
Avoid changing plugin settings unless required for your application's technology or recommended by Ranorex Support.
Restart the application
After applying or changing instrumentation:
- Close the application under test completely.
- Close related processes if necessary.
- Apply the required instrumentation.
- Restart the application.
- Open Ranorex Spy and track the application again.
Some instrumentation changes are not applied to processes that were already running.
Technology-specific issues
CEF applications
If the warning occurs with a Chromium Embedded Framework application, verify that CEF instrumentation has been configured correctly.
See CEF and SAP applications for technology-specific causes and solutions.
Web applications
Verify that the required browser integration is installed and enabled and that the browser version is supported by your version of Ranorex Studio.
Mobile applications
Verify that the application and device have been prepared for mobile testing.
When upgrading Ranorex Studio or changing the Ranorex Service App version, you may need to instrument and deploy the mobile application again.