CEF
When testing CEF applications, you may come across a technology limitation warning. Here are potential causes and solutions for these technology warnings.
Another application is already listening on the remote debugging port
UI elements in your AUT can’t be identified because another application is blocking the remote debugging port (e.g. Chrome DevTools). Close the blocking program and restart the AUT.
Solution:
Ranorex Studio normally tries to close the blocking application automatically. In some cases, like for the Chrome Developer Tools, this doesn’t work. In this case, simply close all applications that may be connected to the AUT at the remote debugging port you specified.
If this fails, you can also try to change the remote debugging port number for the AUT.
Remote debugging is not available
UI elements in your CEF AUT can’t be identified because the remote debugging port isn’t enabled in your AUT or can’t be found.
Solution:
Make sure you’ve activated the remote debugging port correctly (i.e. in source code if required) and that no other applications are using it. If you’ve set the remote debugging port number to something else than 8081, try resetting it to this value.
SAP
For SAP applications you may find the following issues:
Insufficient privileges
Solution: Restart all Ranorex tools and the AUT with the same privileges, preferably as an administrator.
Element identification issues
Solution: Make sure your environment is configured with High Speed Connection (LAN), as Low Speed Connection (Reduced Network Traffic) can impact the functionality of the SAP GUI when using Windows.
