Help documentation

Configure Selenium 2 (WebDriver)

The Selenium 2 configurations are defined in the twist.properties file. You can configure Selenium 2 by "Editing Twist Properties"

GUI for editing Selenium 2 properties, depending on chosen browser, may appear as below:

Edit Selenium 2 properties

Selenium 2 options on Twist properties file

The browser type and other configuration options can be defined in the twist.properties file.

The following Selenium 2 options are supported in Twist:
  • webdriver.browser (Browser): This is used by Selenium 2 to launch the browser. Possible property codes for browser are chrome, firefox, ie, htmlunit, iphone, android. Note, on the properties gui they will be displayed as Chrome, Internet Explorer etc.
  • webdriver.browser.script (Browser Script Location- optional): This is the path of the browser launcher file. This can point to a script launching the browser as well. If this property is not provided, webdriver looks in the standard browser locations (eg. "c:\Program Files\Internet Explorer\iexpolre.exe" for IE in windows)
  • webdriver.browser.profile (Browser Profile - optional): This is the path where a browser profile exists, either for FireFox or Chrome.
  • webdriver.browser.nativeEvents (Enable Native Events - optional): This is applicable for Firefox browser and to enable native event interaction with OS. Default is false.
  • webdriver.reap_profile (Reap Profile - optional): Should be "true" if temporary files and profiles should not be deleted.


  • HtmlUnit specific Options:

  • webdriver.browser.version (Browser version - optional): This setting is only applicable for HtmlUnit and indicates the browser HTMLUnit may configure for. Possible values are FIREFOX_3, FIREFOX_3_6, INTERNET_EXPLORER_6, INTERNET_EXPLORER_7, INTERNET_EXPLORER_8.
  • webdriver.browser.javascriptEnabled (Enable Native Events - optional): Whether HtmlUnit JavaScript capabilities should be enabled.


  • Chrome Driver Specific options:

  • webdriver.chrome.driver (Chrome Server - optional): This setting is only applicable for chrome driver.

    This field represents the location of custom chrome server. Alternatively, we may set the System Property WEBDRIVER.CHROME.DRIVER to use the custom chrome server location. If the custom Chrome server location is not set using twist.properties or system properties, then the Chrome driver bundled with twist is used.



  • iPhone and Android Driver Specific options:

  • webdriver.mobile.server (Mobile Server URL): Specify the full URL of the remote client. This setting is only applicable for iPhone and Andoid driver.