Testing Embedded Chrome Applications

An embedded Chrome application is a desktop application with an embedded web browser engine that is based on the Chromium core. Such applications enable you to add web browser capabilities to a desktop application. You can create such an app by using for example the Chromium Embedded Framework (CEF) or the Electron framework.

Silk4NET provides full support for testing embedded Chrome applications that allow remote debugging through the --remote-debugging-port command line argument. Silk4NET does not support testing embedded Chrome applications that are based on Java, for example Java AWT and Swing applications.

To test an embedded Chrome application with Silk4NET, you have to set the debugging ports for the executable of the application. Start the application from the command line and set the remote debugging port.

Silk4NET checks if the -remote-debugging-port argument is set in the command line arguments of the embedded Chrome application. If the argument is set, Silk4NET automatically sets the Enable embedded Chrome support field to the appropriate executable and debugging port.
If the -remote-debugging-port argument is not set in the command line arguments of the embedded Chrome application, you have to manually specify the executable and the port in the Enable embedded Chrome support field:
1. In the Silk4NET UI, select Edit Options.
2. In the Options dialog, select the Advanced tab.
3. In the Enable embedded Chrome support option, specify the executable and the port as a comma-separated value pair:
```
<application name>.exe=<port number>
```

Note: You cannot test embedded Chrome applications that do not allow remote debugging with Silk4NET.

Note: Silk4NET does not support testing non-browser menus of Electron apps.

Example

For example, you can start the application myApp from the command line as follows:

myApp.exe --remote-debugging-port=9222

You can then specify the executable and port in the Enable embedded Chrome support option as follows:

myApp.exe=9222