If you are getting the above error, you must have downloaded Selenium 3.0.0 Beta and Firefox browser version > 48.0. The latest version can be downloaded from What has changed now? What has changed now? What is gecko and what’s the relation with Selenium scripting? Exception in thread “main” : The path to the driver executable must be set by the system property for more information, see. WHAT! It used to work perfectly fine with Selenium 2.0. Many of you must have encountered a geckodriver error as you start scripting for Mozilla Firefox using the latest Selenium 3.0.0 Beta release.

The latest version can be downloaded from Ī simple resolution of the exception being setting the property.Follow ' Software Testing Studio' at LinkedIn & learn Selenium on the way! Hence, we get the below exception while working with FirefoxDriver without setting the “” property-Įxception in thread “main” : The path to the driver executable must be set by the system property for more information, see. Adding the geckodriver.exe in the system path allows running the driver commands via the GeckoDriver server. So, all the webDriver commands are now required to be served by the GeckoDriver server. But with Selenium 3.0 Mozilla provided its own WebDriver implementation which required GeckoDriver for serving webDriver requests. This is because before the Selenium 3.0 release, the WebDriver implementation of Firefox was developed by guys from Selenium Project only. Now, the question arises why were we not required to add the Geckodriver in earlier versions of Selenium Webdriver(before Selenium 3.0). Hence, the path to the Geckodriver is required to be added in the System path while working with the Firefox browser in Selenium Webdriver. Geckodriver is a server that serves webdriver requests from Gecko-based web browsers like Firefox. Gecko is an open-source web browser engine used in Firefox and other applications developed by Mozilla.

Mozilla geckodriver selenium