Available in WebDriver Set

Chrome Driver Configsince 1.1.0

Introduction

Add this configuration to enable browser based performance testing using Chrome. This document covers the various configuration options available on the Chrome browser. For an overview of performing client sider performance testing, refer to the Web Driver Tutorial.

Different browsers have different levels of setup complexity. In the overall scheme of things, using a Chrome Browser is considered to have a medium level of setup complexity.

Note: For Chrome to work, it is important to specify the location of the Chrome Driver Binary in the Chrome tab

On startup, the user is presented with the following:

The main part of the Chrome configuration UI lies in the tabs:

  1. Proxy
  2. Chrome
  3. Experiemental

Proxy

The default configuration (Use system proxy) is suitable for most. However, if you operate within a corporate network (that use http proxies), then this section may be important to you.

No proxy

Use this option if you directly connect to the internet, and your network will not make use of any proxies.

Auto-detect proxy settings

Some networks will automatically transmit the proxy configuration. This is especially true for Microsoft Windows networks that make use of WPAD/PAC to transmit the proxy configuration to its host.

Use system proxy settings

This is the default configuration, and will make use of the network and/or proxy settings configured for your Operating System.

Manual proxy configuration

This is the most involved, but also allows for the most control of you proxy settings.

HTTP Proxy/Port

Specify the name/IP Address of the HTTP proxy server and its associated port to use when the browser makes external network connections.

Use HTTP proxy server for all protocols

By default this is checked, as most environments use the same HTTP Proxy server for its SSL, FTP and SOCKS connections. However, if this is not the case, then uncheck this option, and override the settings for the other connections.

HTTPS Proxy/Port

Specify the name/IP Address of the HTTPS proxy server and its associated port to use when the browser makes external network connections.

FTP Proxy/Port

Specify the name/IP Address of the FTP proxy server and its associated port to use when the browser makes external network connections.

SOCKS Proxy/Port

Specify the name/IP Address of the SOCKS proxy server and its associated port to use when the browser makes external network connections.

No Proxy for

This is a comma separated list of all host(s) and/or IP Address(es) that will bypass the proxy server.

Automatic proxy configuration URL

For networks that have a proxy configuration server (PAC), and its name and the location of the PAC file is known, please use this option. The usual configuration for this is http://proxy-server/proxy.pac

Chrome

For Web Driver controls to work against Chrome, it is important to:

  1. Download the chrome driver for your Operating System.
  2. Unzip the binary to a specific location
  3. Specify the chrome binary in the input field in this tab.

Since v1.3.0 of JMeter-Plugins:

ChromeDriver can now be used to control Chrome on Android. To enable this check the Use Chrome on Android* checkbox. * You can read output logging from Developer Tool, just use the following code:
var logPkg = JavaImporter(org.openqa.selenium.logging)
WDS.sampleResult.sampleStart()
WDS.browser.get('http://yoursite.com')
var logEntries = new logPkg.LogEntries(WDS.browser.manage().logs().get(logPkg.LogType.BROWSER));
logEntries.forEach(function(entry)
{
   WDS.log.info(entry.getTimestamp() + " " + entry.getLevel() + " " + entry.getMessage()); 
})
WDS.sampleResult.sampleEnd()

Experimental

As new features from the Roadmap are added, new and experimental features will generally get added to this section first. This allows the early adopters to use these features and provide feedback on them. However, it should be recognised that all features added to this tab are subject to change/removal so depend on them at your own peril!