Exception running Jmeter script with the jjp@gc - Chrome Driver Config

[sg.to...@gmail.com]

I'm trying to run a simple test including only jp@gc - Chrome Driver Config element and jp@gc - WebDriver Sampler, but unfortunately  getting an exception:

2017-08-31 16:39:42,984 ERROR o.a.j.t.JMeterThread: Test failed!

java.lang.IllegalStateException: The driver executable is a directory: D:\apache-jmeter-3.2\lib

at com.google.common.base.Preconditions.checkState(Preconditions.java:197) ~[guava-19.0.0.jar:?]

at org.openqa.selenium.remote.service.DriverService.checkExecutable(DriverService.java:123) ~[selenium-remote-driver-2.52.0.jar:?]

and the browser isn't opening.

I'm using "No proxy" config selection.  

Sampler's JS contains only:

WDS.sampleResult.sampleStart()

WDS.browser.get('http://google.com')

WDS.sampleResult.sampleEnd()

Chrome version 60.0.3112.113 (Official Build) (64-bit) on Windows 10. I also tried the latest guava-23.0.0

[gli...@gmail.com]

Looking into 

 The driver executable is a directory

You have improperly configured Chrome Driver Config

1. Download the latest ChromeDriver Executable and unpack it somewhere
2. Put the full path to chromedriver.exe into "Path to Chrome Driver" input (on "Chrome" tab) of the Chrome Driver Config

For more information on using WebDriver Sampler check out The WebDriver Sampler: Your Top 10 Questions Answered article the most common WebDriver Sampler problems solutions. 

[Mani Renukuntla]

similar issue,

I'm running a test using "jp@gc - Chrome Driver Config" in the docker container. 

I'm providing the path as "chromedriver", as I mentioned "WKDIR" as /jmeter.

I'm facing the below error:

My driver location is /jmeter/chromedriver

[Dmitri T]

As per your attached image:

You've set up Chrome Driver Config to look use /jmeter as a ChromeDriver executable and according to your Dockerfile it should be /jmeter/chromedriver

Amend your chromedriver configuration and it should fix your issue.

Also if you're running Chrome as root you should set --no-sandbox command-line argument

And last but not the least:

1. You're using JMeter 5.5 and according to 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article you should use the latest version of JMeter so consider upgrading to JMeter 5.6.2 
2. You're using WebDriver Sampler 3.3 and you should upgrade to 4.10.0.0