Unable to open Edge browser

Tools RIDE
1

I have the latest stable Python, wxPython, Robot Framework, RIDE v2.1 installed. RIDE is happily working with Chrome on my computer. However, I am not able to launch any URL with the Edge browser. I have the matching Edge browser driver installed properly. Below are the error messages I’ve got. Any help is appreciated!

Cmd console log

DevTools remote debugging is disallowed by the system admin

Robot console log

P1.1_UID-P1.2_CP-P2.1_AB-P2.2_Y-P2.3_TN1-P2.5-P2.6_BN-P2.6_CC-P3_Submit | FAIL |
Setup failed:
SessionNotCreatedException: Message: session not created: DevToolsActivePort file doesn’t exist

2

Does your tests works on Chomre browser ?

Looks like your professional computer have restricted access as a user due to the system policy applied by the company on employee’s computers.

1- Try to find out how to enable the " remote debugging feature " in windows or maybe EDGE browser ( I think that’s impossible because it requires admin privileges )

2- Contact your system administration (IT support) colleague to get some help to solve this access/ policy issue

1 Like
3

Yep, my tests work fine on Chrome browser.

Thanks for your suggestion. I was thinking about the same “remote debugging feature” option in Edge browser. Any chance RIDE offers an option to bypass this remote debugging? I imagine many professional places may have this kind of policy enforced.

4

RIDE behavior should be the same as running robot from the command window.

You should try to run your test from a command window, to confirm the problem is independent of RIDE.

1 Like
5

I just tried the command line. I got the exact same error message for Edge browser. Chrome is still fine.

1 Like
6

What Edge version are you running and the driver? I’ve seen posts related to Chrome versions, so could it be worth double checking you have the right driver version for Edge?

This may help as well:

  1. Go to edge://flags in Microsoft Edge
  2. In Search flags, type Enable remote debugging through Windows Device Portal
  3. Set the flag to Enabled
  4. Click Restart to restart Microsoft Edge

Theres a cmd line argument as well: msedge.exe --remote-debugging-port=9222

Also fell on a post about running headless; are you running headless and have you tried when not in headless if so to see if the same error is returned?

7

My Edge is running version 130.0.2849.80. It matches the driver I downloaded from here https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/?form=MA13LH, the current stable one.

edge://flags has been blocked on my computer by the system administrator. This is why I’d like to know if there is an option in RIDE that can bypass remote debugging to at least get Edge going.

I searched here robotframework/doc/userguide/src/Appendices/CommandLineOptions.rst at master · robotframework/robotframework · GitHub, but I don’t see such argument, msedge.exe --remote-debugging-port=9222.

I am very interested in knowing how to run headless Edge in RIDE. For Chrome, the argument is “headless chrome”, but for headless edge it looks like not supported in RIDE.

1 Like
8

Please, consider RIDE just an editor for test cases. When you Run them, you are passing arguments to robot.

About your problem, you should see SeleniumLibrary documentation, here: https://robotframework.org/SeleniumLibrary/SeleniumLibrary.html#Open%20Browser

See that there is no headless Edge driver. Search the Internet about that.

Also, if you have a good solution with Chrome, why not just use that one for testing?

9

Testing needs to be done on both Edge and Chrome. For Chrome, I just don’t get this error “DevTools remote debugging is disallowed by the system admin” when I try to launch a URL, not that I have a magic solution.

10

Hi Cai,

Since 2020 Edge has been based on Chromium, the same browser that Chrome is based on, they use the same rendering engine.

The best options I see that you have are:

  • Ask for a change to the requirements based on this, that only 1 browser needs to be tested for each rendering engine that needs to be supported, this will greatly simplify your testing as there are only a few rendering engines ( the 3 most common are chromium, gecko and webkit)
  • If you can’t get the requirement changed, then you log a call with your IT help desk to have the remote debugging flag enabled for all your test machines and all test user accounts, you can point to the business requirement as your justification. Make it the security team’s problem not yours, they can argue with the business about whether or not the requirement is valid. In the mean time your test reports can just refer to the help desk ticket number for the edge testing.

Hope that helps,

Dave.

11

Haha Dave, great minds think alike. I’ve already opened a ticket with my IT service, but I have a feeling it is going to be like pulling teeth. To be fair, I know Selenium IDE somehow doesn’t have issue on Edge browser, and my colleague can make Robot + VS Code work on Edge without this issue.