Any plans to support Microsoft Edge browser?

[galatrash]

Are there any plans to add support for Microsoft Edge browser in the near future?

[lefthandedgoat]

I have to do some research on that. I don't know how selenium and edge work together. I will do that this afternoon and let you know. Hopefully its as simple as an driver for edge.

[galatrash]

Here is where to obtain the web driver for Edge
https://www.microsoft.com/en-us/download/details.aspx?id=48212

[lefthandedgoat]

I have this 'working' on another branch, it has some issues:

There are actually 3 different 'Webdrivers' and the one you linked is the oldest one. Read the last comment here: https://blogs.windows.com/msedgedev/2015/07/23/bringing-automated-testing-to-microsoft-edge-through-webdriver/

To me that is a problem because google is not finding the right webdriver, and MS isn't doing a good job of representing them (good version numbers, listed out on a page with all downloads there).

~20% of the tests in my regression suit are failing. Selenium Actions (drag/drop), some javascript functions, interacting with js alerts... none of these things seem to work.

I can get my test suite to run with debugger, or bash ??, but not from normal windows command prompt. A browser is launch and it hangs there.

I honestly feel Edge isn't ready for prime time automation testing, but if you want I can add it. I will call it EdgeBETA or EdgeUseAtOwnRisk or something to make it clear that it is not on the same level as other browser.

Thoughts?

[galatrash]

Sounds good to call it a beta support. At least those who want to test without these edgy issues can do some verification using this beta.

[lefthandedgoat]

Added here, I will do a nuget build soon: #265

just use

start edgeBETA
After installing the right webdriver, which for me (fully updated windows 10) was the Fall 2015 one.

[lefthandedgoat]

https://www.nuget.org/packages/canopy/0.9.54

Enjoy and good luck!

[galatrash]

I've tried the new code, but every time I call start edgeBETA I receive an error like this:

[10:31:33.704] - Listening on http://localhost:3904/
System.InvalidOperationException: Unknown error
   at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
   at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
   at OpenQA.Selenium.Edge.EdgeDriver..ctor(String edgeDriverDirectory, EdgeOptions options)
   at canopy.core.start(BrowserStartMode b) in C:\Projects\canopy\src\canopy\canopy.fs:line 696

BTW, I tried with all the 3 available EDGE web drivers and I get the same error in all.

[lefthandedgoat]

Does it launch an instance of Edge?

[lefthandedgoat]

Also can you tell me what version of edge you have? I have 25.10586.0.0

[galatrash]

It launches an instance and closes it right away. I have this version:
Microsoft Edge 25.10586.0.0
Microsoft EdgeHTML 13.10586

[lefthandedgoat]

Can you try the code in this blog post and see if it works for you?

https://blogs.windows.com/msedgedev/2015/07/23/bringing-automated-testing-to-microsoft-edge-through-webdriver/

[galatrash]

It does the same thing and giving me the same error: System.InvalidOperationException: Unknown error

[lefthandedgoat]

Look in your C:\Program Files or C:\Program Files(x86) and see if there is a Microsoft WebDriver folder. You can add that path to this line of code in the c# example

driver = new EdgeDriver(@"C:\ADD\PATH\HERE");

And see if that works.

Also maybe try to uninstall the drivers (add remove programs I think) and then install the Fall 2015 one.

Beyond that.. I dont know =( other than googling the error and seeing if something comes back.

[galatrash]

Thanks for your effort. I tried with all the versions of the driver and no matter what I did, the same error occurs. Googling didn't find anything. I may need to test on a different Windows 10 machine to see if it works. If it still not working, I will wait for a newer driver version o check.

[lefthandedgoat]

Ok sounds reasonable. I have it 'working' in my VM, so if you ever need to compare version numbers etc, let me know.