i am using selenium 1.0.2 for my automation test cases, when i try to execute it from ie browser ,its launching , but its failing when hits driver. findelements or even waituntil saying
The HTTP request to the remote WebDriver server for URL http://localhost:39208/session/61215720-0870-47fa-a50b-ac97fb8b7bbc/window_handles timed out,
but same test case is passing in chrome. also have found the in ie it passes if i use the url - http://omnichannelint.blob.core.windows.net/convcontrol-daily/HTML/AgentWidgetWithMock.htm , failes when i use file:////C:/WebResources/HTML/AgentWidgetWithMock.htm have tryed same in localhost:8080 then also it fails, please any one help me fix this issue
Related
I can no longer use DevTools remote debugging port api calls from a chrome driver instance that was started by selenium + chromedriver.
Previously we could use the dev-tools port using chrome-remote-interface.
Now, when I use chrome-remote-interface, the selenium webdriver seems to be unusable.
So for example, let's say I:
driver = new ChromeDriver()
Then I do this to go to a site:
driver.get("https://some-site.com")
So far so good.
Then I use the remote-debugging-port to make request as well.
See: https://github.com/cyrus-and/chrome-remote-interface for an example.
This also works.
Now I try to use the Java web driver again:
driver.get("https://some-site.com")
And I get an error:
[1651087065.452][INFO]: Done waiting for pending navigations. Status: timeout: Timed out receiving message from renderer: 0.000
[1651087065.452][INFO]: [4ac1553138574d061b37a45836c35096] RESPONSE GetCookies ERROR timeout: Timed out receiving message from renderer: 0.000
(Session info: chrome=100.0.4896.127)
[126480:126508:0427/141746.195721:ERROR:cast_crl.cc(391)] CRL - Verification failed.
I created an issue tracker: https://bugs.chromium.org/p/chromium/issues/detail?id=1320455&q=reporter%3Ame&can=2
Does anyone know a solution to this?
You no longer need to use chrome-remote-interface to access the chrome debugging port. You can now use Selenium 4's new ChromeDriver dev tools SDK to execute commands against chrome through the CDP.
Switching to this fixed the problem.
I need a help on identifying a selenium testing issue on jenkins slave.Initially the chrome browser was not launched and we found the chrome driver version is not matching with chrome browser version. After we fixed that now we are getting error as Expected enabled element was not enabled
From Jenkins Console Log
But we are able to load the payload html page and able to see the element as like below
From HTML File
From browser
Same code is working fine in other jenkins servers. So why it is stating as the element is not visible even though we are able to see in payload html? Is there any additional settings we have to do from jenkins slave?
Could you please guide me.
In a web application, the browser launched from selenium webdriver throws internal server error.
Manually opening the same web application works fine.
I tried to delete the cookie in the browser launched from driver when I got error and once cookie is cleared and refreshed, I am able to get the application.
I have tried driver.manage().deleteAllCookies() which dint work.
Any suggestions for me please?
I have a Selenium automation suite up and running with chrome which works like a charm. I have integrated IEdriver within. After integrating I executed few of the test cases and getting problem with the execution on IE11. I observed that my test fails with the exception "HTTP request to the remote WebDriver timed out after 60 seconds" . This behavior is random for every run and in continuing tests, pop up window is always logged out in application. Did anyone face similar problem?
You could maybe increasing the timeout?
InternetExplorerDriver driver = new InternetExplorerDriver(#"c:\pathtoie", options, TimeSpan.FromMinutes(2));
I was doing development and test execution on VM and whenever I lock my system, the script hangs on the VM. So doing execution on a VM from different VM will solve the problem.
I have a weird problem going on with a Selenium test. I have an internal company website that I'm writing a Selenium test for and am getting a 404 error ONLY with the browser instance that Selenium opens up. It doesn't matter if its Chrome or Firefox, I still get the 404.
To prove its only with the browser instance that Selenium opens I have run my test in debug mode, paused it when the browser launches and then manually executed the test case within that browser instance and I always get a 404.
Now, if I open a normal Chrome or Firefox browser instance outside of Selenium I can manually execute the test case just fine.
Manual execution of the test case in Chrome Incognito also works.
What am I missing here?
Apparently something else needs to be loaded with in the browser but I have no idea what. Any help would be greatly appreciated.
I found that we had a redirect problem on our server, however it still doesn't make sense as to why it failed in WebDriver but not in a normal browser. Either way, its resolved.