Testing of CEF applications

Ranorex Studio supports testing of applications based on the following CEF technologies:

• Chromium Embedded Framework (CEF)
• CefSharp
• Electron
• NW.Js
• Qt WebEngine
• JxBrowser

To enable CEF testing, you need to enable the remote debugging port in the AUT. This page explains how to do so.

For most CEF technologies, adding the following command line argument (for example, to the Run application action in a recording module) when starting the AUT is sufficient:

MyApplicationUnderTest.exe –remote-debugging-port=8081 --remote-allow-origins=*

Attention
Based on the example above, remote debugging uses port 8081. However, Ranorex Remote Agent also uses port 8081, which can lead to conflicts.
- If the Remote Agent is running, your AUT cannot bind to port 8081.
- If the AUT is using 8081, the Remote Agent cannot start.
It is recommended to use a different, unused port (e.g., 9222) for remote debugging when the Remote Agent is active.

However, some technologies require a different approach.

CefSharp

If your AUT is based on CefSharp, the command line argument does not work. Instead, enable the remote debugging port in the source code of the AUT.

To set the remote debugging port in CefSharp, you have to specify it with the help of the CefSettings class before initializing the control as follows:

var settings = new CefSettings();
settings.RemoteDebuggingPort = 8081;
Cef.Initialize(settings);

JxBrowser

If your AUT is based on JxBrowser, the command line argument does not work. Instead, enable the remote debugging port in the source code of the AUT by calling the BrowserPreferences.setChromiumSwitches(String…) method.

Please refer to this article in the official JxBrowser documentation to see how.

Please refer to CEF and SAP Applications for some possible instrumentation issues and their solutions.