To automate web tests in Google Chrome or Microsoft Edge, you must install the Ranorex Automation add-on. The process for both browsers is nearly identical.
Install the add-on via Instrumentation Wizard
You use the Instrumentation Wizard to deploy the extension to your preferred browser.
For Google Chrome
- Open the Instrumentation Wizard. For more information, see UI Technologies Introduction.
- Select Instrument a browser.
- Enable the Chrome slider and click Next.
- Once the Instrumentation successful message appears, click Finish.
- Restart the browser and click the Extensions icon to verify the installation.
After installation, the Customize and Control Google Chrome settings display the “Managed by your organization” message. This message remains even after uninstalling Ranorex Studio. For information on how to remove it from your browser, see Stop managing or delete Chrome browsers and profiles.
For Microsoft Edge
- Open the Instrumentation Wizard. For more information, see UI Technologies Introduction.
- Select Instrument a browser.
- Enable the Microsoft Edge slider and click Next.
- Once the Instrumentation successful message appears, click Finish.
- Restart your browser.
- Click the browser menu icon that shows a warning symbol and select the Ranorex Automation extension has been added message.
- Click Enable extension.
Manual installation
If you prefer not to use the wizard, you can install the add-on manually.
- Type chrome://extensions (Google Chrome) or edge://extensions (MS Edge) into the address bar.
- Click Load unpacked.
- Navigate to the Ranorex Chrome Extension folder in your Ranorex Studio installation directory and click OK.
-
Register the Chrome/Edge worker Ranorex.Plugin.ChromeMsgHost.manifest file in the Windows Registry to enable communication between the browser and Ranorex.
-
For Google Chrome: Open the Registry Editor (
regedit) and add the manifest file path to the following keys:HKEY_CURRENT_USER\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.ranorex.chrome_msghostHKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Google\Chrome\NativeMessagingHosts\com.ranorex.chrome_msghost
-
For Microsoft Edge: Add the manifest file path to the following keys:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Edge\NativeMessagingHosts\com.ranorex.chrome_msghostHKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Microsoft\Edge\NativeMessagingHosts\com.ranorex.chrome_msghost
-
For Google Chrome: Open the Registry Editor (
Important notes for testing with Google Chrome/MS Edge
- If you want to test cross-domain iframe scripting, start the browser with the command line argument
–disable-web-security –user-data-dir=”” - Make sure that the extension ID of the Ranorex Add-on is listed in the allowed_origins section of the
binRanorex.Plugin.ChromeMsgHost.manifestfile. - If the NoScript Extension is installed, disable it.
Configuration for local files
To test offline or local HTML files, enable the Allow access to file URLs option for the Ranorex extension in both Chrome and Edge. After enabling this option, restart the browser.
Host permissions
Chromium-based browsers follow the same core rule as Firefox: you cannot silently escalate host permissions at runtime in unmanaged environments. If a permission prompt is required, the user must approve it.
✅ What is possible (managed enterprise environments)
Enterprise environments can preconfigure site access using ExtensionSettings policies (for example, allowing runtime host permissions through managed policy).
Windows registry paths (examples)
- Chrome:
HKLM\Software\Policies\Google\Chrome\ExtensionSettings - Edge:
HKLM\Software\Policies\Microsoft\Edge\ExtensionSettings
Example policy value:
{
"installation_mode": "allowed",
"runtime_host_permissions": {
"allowed_hosts": ["*://*/*"]
}
}This can give the extension full host permissions without requiring a user-facing toggle, as long as the browser is managed through enterprise policies.
❌ What is not possible (non-managed browsers)
- Silently modifying permissions for a non-managed browser
- Auto-granting optional host permissions at runtime
- Bypassing permission prompts
- “Faking it” through UI automation (fragile and unsupported)