The following sections describe how to get started with WebDriver for Microsoft Edge. The previous, browser-specific driver for Microsoft Edge (EdgeHTML), which is also known as Microsoft Edge Legacy. To run legacy end-to-end tests for Internet Explorer Mode, we recommend using Internet Explorer Driver. One such framework is Selenium.Īn open-source implementation of the WebDriver protocol specifically for Internet Explorer. WebDriver testing frameworks exist for all major platforms and languages. Provides a language-specific interface that translates your code into commands that are sent to Edge WebDriver. Test authors use a testing framework to write end-to-end tests and automate browsers.

Edge WebDriver is then responsible for communicating that command to the browser. Test authors write tests that use WebDriver commands that Microsoft Edge WebDriver receives. Microsoft's implementation of the WebDriver protocol specifically for Microsoft Edge. This protocol allows out-of-process programs to remotely instruct the behavior of web browsers. The functional relationship between these components is as follows: TechnologyĪ W3C standard for a platform- and language-neutral wire protocol. To automate Microsoft Edge with WebDriver to simulate user interaction, you need three components: Relationship between WebDriver and other software WebDriver runs multiple sessions of Microsoft Edge on a specific machine. WebDriver manages multiple windows, tabs, and webpages in a single test session.

WebDriver simulates user events or OS-level events more accurately than JavaScript unit tests. WebDriver accesses functionality and information that's not available to JavaScript running in browsers. Tests that use WebDriver have some advantages over JavaScript unit tests that run in the browser:

WebDriver allows you to automate Microsoft Edge by simulating user interaction.

Edge beta browser