Running with Edge(Chromium) not working

[Polariteit]

Hi there,

The webapplication under test is going to migrate to MS Edge (chromium) later this year, so I'm investigating how our testscripts are running on the new Edge browser.

When running a usercode module to start the browser and go to a login-page of our app; than Edge fails to find the fields on screen to enter the username and password. The browser is started and opens the correct URL, but then it stops and nothing happens.

The EDGE-plugin is installed and activated. When I do the same test, but with IE11 or Chrome, then it succeeds in finding the fields and continues.

Do you have any suggestions?

Edge version: Versie 81.0.416.53
Win10
Ranorex 9.3.1

[odklizec]

Hi,

Have you tried to manually track an element with Ranorex Spy? Does it work (Spy should track the element and xpath should start with DOM)?

Also, have you added Edge to Ranorex white list?

Whitelist.png (5.55 KiB) Viewed 338 times

[carloagiletester]

I am having the same issue here. It opens the browser. But Ranorex Spy does not see any the Domain entry.
I whitelisted Edge(Chromium), but that did not make any difference.
Version 9.3.1 and windows server 2019 standard 1809

[odklizec]

Hi,

If Spy don't see DOM element in browser, then there may be two reasons:
- not installed Ranorex plugin
- corrupted Ranorex plugin
Are you sure there is installed Ranorex plugin in your instance of Chromium based Edge?
If plugin is installed, but Spy still don;t see DOM, the plugin integration is most probably corrupted. In this case, you should try to uninstall it via Instrumentation wizard and then install it back.
BTW, make sure Edge is not running in background after closing its window! This is a default Edge/Chrome behavior and it must be turned off before installing/uninstalling Ranorex plugin. Go to browser's settings and search for "Continue running background apps when Google Chrome/Edge is closed" and uncheck it.

[Polariteit]

I'm sorry about the late response, but it finally worked. The solutio Odklizec about reinstalling the extension through the instrumentation wizard did the trick. You have to deinstall and install the extension through the wizard, otherwise it won't work.

Thanks guys!