Webdriver -EDGE Browser- Scritps Run in Headless ?

By design Issue #14057655

Details

Author
Santosh
Created
Oct 3, 2017
Privacy
This issue is public.
Reports
Reported by 4 people

Sign in to watch or report this issue.

Steps to reproduce

Hi,

Would like to know whether we can run webdriver scripts in Edge browser - Headless Mode ? (Without loading GUI). If so, please let me know the details.

Thanks,
santosh

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Steven K.”

    • Good question.  Let me find out.

      Steve

    • Edge does not yet support headless mode.

      It is a missing feature that we are aware of.  There is already a uservoice entry for it.  Vote for it.  :)

      https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6545168-headless-browser-for-testing

      Appreciate the question,

      The MS Edge Team

    • Microsoft Edge Team

      Changed Status to “By design”

    • MICROSOFT EDGE TEAM and Steve K, you guys are a bunch of losers. One major thing that held IE back is the fact that’s is crap for automation, you lost the SDET community. Instead of making Edge super testable, you’re missing major testability features that are on other older browsers. You don’t get it. Yes, you guys are a bunch of losers.

    • You’re waiting for the community to raise noise before you support something you should really have supported from day 1? No wonder. A bunch of losers.

    • Couldn’t agree more.

    • I’ve generally been impressed with Edge, even though I shunned IE nearly two decades ago and never looked back. However, the fact that there is no headless mode indicates MS is still behind the times WRT modern development practices, which demand automated testing…something that is made much more cumbersome without headless capabilities. I’d really like to see Edge succeed…but this makes it significantly harder for organizations to ensure their apps work with your browser. :(

    • I really like Edge but it’s not suitable for automated testing for two reasons:

      • issues with XPATH evaluation (really a blocker)
      • inability to run headless (more like critical, even if first point is resolved I would abstain from using Edge in tests unless I have no other choice)

      Given that it takes literally years for Edge team to address XPATH issues, eg. https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/8503401/ I am not holding my hopes high for this one

    • I don’t think Edge has a future unless 1) it goes open-source and 2) its release cadence gets decoupled from the OS releases. I used to be expert in IE WebBrowser Control hosting and re-using, and I must say, the the level of programmabilty and interfacing documentation of IE was top notch compared to Edge. No matter how good Edge is internally, it’s getting increasingly irrelevant to developers outside Microsoft. It’s sad but I expect we’ll see more and more Electron-based applications, including from Microsoft itself, making the whole Windows itself less and less relevant.

    You need to sign in to your Microsoft account to add a comment.

    Sign in