I am trying to run a Jmeter test on remote machine ( macOS sierraO).
I configured jp@gc - Chrome Driver Config
and I can connect to the slave machine. However,
I could not pass any parameters to chromedriver
from p@gc - Chrome Driver Config
directly, my config looks like:
where my chromedriver.dir
was chromedirver.dir=vu.chromedriver.dir=/path/to/chromedriver
However, I was able to work around it by adding:
workaround.sh
for macOS
#!/usr/bin/env bash
/path/to/chromedriver --whitelist-ip $*
workaround.bat
for Windows
\\src\\path\\to\\chromedriver.exe --whitelist-ip %*
And that solved my issue for making chromedriver to accept remote connections.
I had the same issue. I fixed by changing to Chromedriver version 80.0.3987.106
lease protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
Solution: Get your Chrome Browser version and download the ChromeDriver for specific to that version.
Open your Chrome browser > Click on 3 vertical dots (top right corner) > Help > About Google Chrome
Verify the Chrome Version (such as 73 or 74 or other ..)
goto Selenium browser driver download portal and download the Chrome Driver of that version
https://sites.google.com/a/chromium.org/chromedriver/downloads