WebDriver Sampler in JMeter

WebDriver Sampler in JMeter

2017 / 8 / 11

Load Testing, Best Practices

Up to this point, performance testing has been on the server side of things as JMeter does not include the time needed to render the response, nor does JMeter process any client code, for example JavaScript . Things that add to the overall browser execution time may include:

Some of the new and noteworthy changes are.

  1. Client-side JavaScript execution - e.g. AJAX, JS templates
  2. CSS transforms - e.g. 3D matrix transforms, animations
  3. 3rd party plugins - e.g. youtube, Double click ads, site analytics, etc.

Hopefully, JMeter eco-system is very rich, so there is a solution for this; we will use WebDriver Sampler in JMeter as this sampler automates the execution and collection of performance metrics on client-side.

To get WebDriver Sampler--https://jmeter-plugins.org/wiki/WebDriverSampler/

Also we need to install the browser Driver plugins of JMeter to run the test on the particular browser like [email protected] - Chrome Driver Config, [email protected] - Firefox Driver Config, etc

Configuration of WebDriver Sampler test:

  1. Add a Thread Group to the Test Plan, and add HTTP Cookie Manager, [email protected] - Firefox Driver Config (from Config Element), [email protected] - WebDriver Sampler (from Sampler) to the Thread Group and a listener View Results in Table.
  2. Write/Add the code in the WebDriver Sampler which you want to test. Here is the sample code, where it says to open www.frugaltesting.com website and to get load time of it:


    FrugalTesting blog on webdriver sampler in Jmeter
  3. Now when we hit play button, JMeter will open a Firefox browser and search www.frugaltesting.com site and end the test as browser closes automatically after performing the actions according to the script (sample script) in the Web Driver Sampler.
  4. We can see the sample result in the View Result Table.
    FrugalTesting blog on webdriver sampler in Jmeter

Configuration of WebDriver Sampler test:

  1. The reader should be prudent in the number of threads they will create as each thread will have a single browser instance associated with it.
  2. As each browser consumes a significant amount of resources, so a limit should be placed on how many browsers the user should create.

FrugalTesting is one stop solution for all your testing challenges. Take your first free Load test here!

Read on to know more about Apache JMeter

You might also like