Selenium Edge driver not getting URL - java

Question

I have recently updated my selenium libraries from 2.46.0 to 2.53.0 (the most recent) in order to run tests on a Windows 10 machine with the Edge browser.

I have add

Answer 1

I had also faced this issue where the Edge Browser was getting opened. But it wasn't loading the website URL and got auto-closed.

I tried this with Selenium 3.0 Beta2 and Windows 10. I got this issue because I was using incorrect version of MicrosoftWebDriver.exe. When I used the correct version of the webdriver, then this issue got rectified.

I used the below steps to resolve this issue -

1. Go to Start > Settings > System > About and note down the OS Build number.

2. Download the proper version of the driver from this link - https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/

3. If the file that's downloaded is .msi, then install it to get the .exe driver. For one of the release, direct .exe can be downloaded.

Sample Script that I used is given below -

System.setProperty("webdriver.edge.driver","C:\\Program Files (x86)\\Microsoft Web Driver\\MicrosoftWebDriver.exe"); //put actual location
WebDriver driver = new EdgeDriver();
driver.get("your link");

You can refer this article, if you want to see the detailed steps - http://automationtestinghub.com/selenium-3-launch-microsoft-edge-with-microsoftwebdriver/

Answer 2

It looks like it is failing to instantiate a new version of the driver. From the stack it also seems to think the operating system is Windows 8 but that might be a bug in Selenium per this line:

'DESKTOP-7LLLD31', ip: '172.16.4.159', os.name: 'Windows 8', os.arch: 'amd64', os.version: '6.2', java.version: '1.7.0_51'

One thing to note is you should always use a matching build of Windows/Microsoft Edge/Microsoft WebDriver. So per your screenshot you are on version 10586 of Windows/Microsoft Edge and should be using build 10586 of the driver which is located here: Microsoft WebDriver Fall 2015 Update

If you are in fact on Windows 10 and running it and seeing this issue then the next area to look at might be capabilities. Try creating an instance without passing in any capabilities and see if that works. If a capability you pass in is required and ends up being incorrect it will cause the creation of the instance of WebDriver to fail.