Why do we need IEDriver and ChromeDriver, but no Firefox driver?

I have little doubt.

Why do we need IEdriver and the Chrome Driver working with selenium scripts in IE and Chrome, but we don’t need the firefox driver to run the script?

Is there a reason for this?

+7
selenium selenium-webdriver
source share
4 answers
  • This is due to the use of the Based browser used in WebDriver.
  • Each browser uses a different JS Engine .
  • All drivers [ Chrome Driver, IE driver, etc., ] are created on the basis of a special JS Engine used by each browser.
  • Selenium offers a built-in driver for Firefox, but not for other browsers. [Not sure if this could happen in the future, because the TestNG and JUnit library files are now part of the standalone Selenium server]
+10
source share

In google direct search FirefoxDriver official documentation

+8
source share

External drivers are the preferred process of Selenium developers. They allow you to manage driver versions closer to the browser than to Selenium, and they can be supported by browser authors (for example, ChromeDriver, OperaDriver). There is a long-standing plan to replace FirefoxDriver with a Mozilla-supported driver based on the Mozilla Marionette architecture.

+2
source share

The Firefox driver is already included in the selenium-server-standalone.jar package.

+1
source share

All Articles