Forum Discussion

BobbyCannon's avatar
BobbyCannon
Copper Contributor
Apr 10, 2019
Solved

UI Automation (edge chromium)

What is the expected method to UI (ux) automate the new Edge (insider) browser? 

  • BobbyCannon we plan on having an MSEdgeDriver very soon, and you can also use puppeteer and headless. In addition, you can use ChromeDriver for the time being by passing in the path to msedge.exe in a ChromeOption. Is there anything specifically you would like? 

10 Replies

  • johnjansen's avatar
    johnjansen
    Former Employee

    BobbyCannon we plan on having an MSEdgeDriver very soon, and you can also use puppeteer and headless. In addition, you can use ChromeDriver for the time being by passing in the path to msedge.exe in a ChromeOption. Is there anything specifically you would like? 

    • CodeDJ's avatar
      CodeDJ
      Iron Contributor

      johnjansen any plans to support IE like automation? we use winforms to do browser automation that launches IE and navigates through website for our customers. Right now, using a WebDriver seems to be a solution more for test automation more than end user automation.

       

      Additionally, when I had tried Selenium with Old Edge, I had to match it to the Windows version which is not in our control. Second, if I remember correctly, I could not release the hook to the selenium launched browser window as ending my program also closed the browser.

      • johnjansen's avatar
        johnjansen
        Former Employee

        CodeDJ I did want to add that we have heard the request about ending your testing application also closed the browser. We have been looking into that. I will say that it sounds like your winforms app for executing the browser is something that WebDriver is meant to do. The goal of webdriver is to replicate the actions of an actual human as we best we can.

    • BobbyCannon's avatar
      BobbyCannon
      Copper Contributor

      johnjansen I have an automation open source project that I want to add support for Edge. 

       

      I would suggest, if you can do this, to stick with the Chrome way of automating. It's uber nice to not have to download yet another thing to get automation working. I never supported Edge due to the fact that I'd have to instruct TestR to download the "driver" to enable support. Just too much friction. 

       

      One of the benefits of TestR over other automation frameworks is that it just works with very little friction. IE and Chrome just works and FireFox has very little configuration requirements. You can reference one nuget package, add a few lines of code, and boom you are automating browsers and desktop applications.

      • satra2806's avatar
        satra2806
        Copper Contributor
        Hi , Could you please help me , i need exactly same , i want to automate lot of stuff using edge browser like controlling windows applications

Resources