So my selenium scripts are getting stuck at driver.get ever since my chrome browser is updated to 107 . The scripts are running fine with browser 105 if I update the chrome script gets stuck at driver.get and gives the error unable to receive message from renderer.
I am using the latest 107 chromedriver , I have updated all the dependencies in pom.xml . Jdk version is 19 .
Related
I am trying to launch the chrome browser and open my site login page,
so once the login pop up appears then this error comes and sometimes this error is not coming at the time login pop up,its coming middle of tests run that is after login has been done and tests starts running
I am using Testng,also in some of code lines I have used Thread.sleep
ChromeVersion : 75
ChromeDriver : 2.46 (Latest version of chrome driver giving some malicious protect error,so using this one)
Error : org.openqa.selenium.WebDriverException: java.net.SocketException: Connection reset
Change your chrome driver version (ChromeDriver 2.46 NOT Supports ChromeVersion 75).
See full documentation:
http://chromedriver.chromium.org/downloads
ChromeDriver 2.46 Supports Chrome v71-73
ChromeDriver 75.0.3770.8 Supports Chrome version 75
ChromeDriver 75.0.3770.90 Supports Chromeversion 75
ChromeDriver 75.0.3770.140 Supports Chrome version 75
I am using Selenium 2.52 and chromedriver 2.29 for chrome browser version 57.
But I could see chrome browser version got updated to latest version 61 in selenium nodes and so tests are failing with "org.openqa.selenium.WebDriverException: unknown error: Element is not clickable
".
So I have updated the chromedriver version to latest 2.33 since the Chrome browser version is the latest.
some tests are getting passed and still, I could see some tests are failing with same error or similar type of error.
Is it required to update Selenium version to any latest version or Selenium 3 to use latest chromedriver?
Your selenium version is an old version. With the latest "browser"driver (ChromeDriver 2.33, in your case) is recommended to use Selenium 3.5 (and greater)
I am trying to run my Selenium tests using Selenium 2.53 and Firefox 54 , it does not work . Has anyone else faced the same problem and have any solutions to it?
Firefox 54 is too new for Selenium 2.53, latest Firefox versions works only with latest Selenium version.
You can download and install Firefox 46 - that should work fine with Selenium 2.53. Make sure to disable auto updates in Firefox.
Or you can update your selenium to latest 3.4.0.
I am trying to run the testcase on centos 6 in chrome browser.
my chrome browser version is 51 and chrome driver is 2.9.
Please help me out. i am running into problems.
I have attached image file which describes the error Unreachable browser excpetion
I have written 3 test cases
1 open the Google site in Firefox browser and search
2 open the Google site in Chrome browser and search
3 Printing some messages,no browser involved
From Eclipse I can run the above test cases properly
if i run testng.xml as testNG site From Eclipse then also all the above test cases running properly
but When ever i am trying to run my webdriver test cases from command prompt through ANT using build.xml
For the chrome browser it showing alert related to manifest version and for Firefox browser its showing error related to Unable to bind to locking port 7054 and my first two test cases getting failed. [ i have attached the fail report of those test cases ]
Can any one give some suggestion what changes are required so that i can run my test cases properly from ant
I am using selenium Webdriver java build [ latest one]
Framework : TestNg
Editor : Eclipse
Firefox browser version : 22.0
Chrome Browser version : 28.0.1500.72 m
OS: Windows 7 Ultimate
I have attached the screenshot related to
1 chrome browser alert
2 chrome browser which opened but not able to open the site
3 Fail report of the test case which involved firefox driver
4 Fail report of the test case which involved chrome driver.
5 Screenshot of my project setup
Checking your system path for a path to chrome and FF might help . That worked for me though I didn't have a similar error.