Why do we need to set the System Property for Chrome And IE Browser and Not For Firefox Browser

Question

For Chrome,

public class Chrome {

  public static void main(String[] args) {

        System.setProperty("webdriver.chrome.driver", "E://chromedriver.exe");
        WebDriver driver = new ChromeDriver();              
        driver.get("http://www.google.com");

    }

}

for Firefox,

public class Firefox {

      public static void main(String[] args) {

            WebDriver driver = new FirefoxDriver();              
            driver.get("http://www.google.com");

        }

    }

Why do we need to specify the system.setProperty for Chrome and IE?

Brambling

Answer 1

I had also same question, but after digging I found,

WebDriver uses native browser approach. Selenium offers inbuilt driver for Firefox but not for other browsers. All drivers (Chrome Driver, IE driver, etc.) are built based on the special JS Engine used by each browser.

Selenium WebDriver works very well with Mozilla Firefox because it has a built in driver server. But the same is not true for Internet Explorer and Google Chrome. Firefox is the most traditional browser, thus Selenium WebDriver do not require any additional utility to be set before launching the browser. The Selenium package automatically references towards the default location of the firefox.exe, thus the user need not to set any other property.

If you ever get the “the path to the driver executable must be set by the webdriver. ie. driver system property” error or its similarly worded Chrome equivalent, it means that you need to install the driver servers on your browser. The driver server manages the calls between the browsers and the Selenium wire protocol.

The InternetExplorerDriver is a standalone server which implements WebDriver’s wire protocol

Similarly, Google Chrome doesn’t have a built-in server so you will need a Chrome driver server for communicating your Selenium code to the browser. You can download the Chrome driver server.

Founded from here.

Elope

Thank you Sanjay.. It really Help to understand the concept behind it. – Brambling

Answer 2

Implementation of FirefoxDriver, ChromeDriver, InternetExplorerDriver is different, thus the way of instantiating the object differs as well.

The Firefox Driver controls the Firefox browser using a Firefox plugin. The Firefox Profile that is used is stripped down from what is installed on the machine to only include the Selenium WebDriver.xpi

The InternetExplorerDriver is a standalone server which implements WebDriver’s wire protocol.

The ChromeDriver is maintained / supported by the Chromium project iteslf. WebDriver works with Chrome through the chromedriver binary (found on the chromium project’s download page). You need to have both chromedriver and a version of chrome browser installed. chromedriver needs to be placed somewhere on your system’s path in order for WebDriver to automatically discover it. The Chrome browser itself is discovered by chromedriver in the default installation path

For more details, refer the selenium documentation

Jiggle

Answer 3

Simple answer is, each browser has its own WebDriver implementation and is not maintained by the Selenium project. Hence for selenium to interact with the browser specific driver we need to specify the full path of the driver.

Why for firefox there is no need to specify the driverpath? In Selenium 2.0, selenium RC is still present and was supporting firefox. From Selenium 3.0 onwards there is no official support for any browser specific drivers. Hence, we need to specify the driver path through System.setproperty for all the browsers.

Fado