Vfrdtyky

I've been using Selenium for a number of months, which we're using to automate some of our internal testing processes. The scripts have been passing fine. I've recently upgraded to C# 2.40.0 webdriver using FF 27.01 and our scripts are now failing in random places with the following error.

[Portal.SmokeTest.SmokeRunTest.Booking] TearDown method failed. OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver server for URL htt(p)://localhost:7055/hub/session/56e99e88-ba17-4d12-bef1-c6a6367ccc2f/element timed out after 60 seconds.

  ----> System.Net.WebException : The operation has timed out

TearDown : OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver server for URL htt(p)://localhost:7055/hub/session/56e99e88-ba17-4d12-bef1-c6a6367ccc2f/window timed out after 60 seconds.

  ----> System.Net.WebException : The operation has timed out

[09:01:20]

[Portal.SmokeTest.SmokeRunTest.Booking] TearDown method failed. OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver server for URL htt(p)://localhost:7055/hub/session/56e99e88-ba17-4d12-bef1-c6a6367ccc2f/element timed out after 60 seconds.

  ----> System.Net.WebException : The operation has timed out

TearDown : OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver server for URL htt(p)://localhost:7055/hub/session/56e99e88-ba17-4d12-bef1-c6a6367ccc2f/window timed out after 60 seconds.

  ----> System.Net.WebException : The operation has timed out

   at OpenQA.Selenium.Support.UI.DefaultWait`1.PropagateExceptionIfNotIgnored(Exception e)

   at OpenQA.Selenium.Support.UI.DefaultWait`1.Until[TResult](Func`2 condition)

   at Portal.Test.Helpers.Process_Bookings.OpenBookings.SelectBooking(String bookingnumber)

   at Portal.SmokeTest.SmokeRunTest.Booking() in d:TeamCityAgentworkdac1dcea7f2e80dfSmokeTestsSmokeRunTest.cs:line 68

--WebException

   at System.Net.HttpWebRequest.GetResponse()

   at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)

--TearDown

   at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)

   at OpenQA.Selenium.Remote.HttpCommandExecutor.Execute(Command commandToExecute)

   at OpenQA.Selenium.Firefox.Internal.ExtensionConnection.Execute(Command commandToExecute)

   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)

   at OpenQA.Selenium.Remote.RemoteWebDriver.Close()

   at Portal.Test.Helpers.Setup.CloseWebdriver()

   at Portal.SmokeTest.SmokeRunTest.TearDown() in d:TeamCityAgentworkdac1dcea7f2e80dfSmokeTestsSmokeRunTest.cs:line 162

--WebException

   at System.Net.HttpWebRequest.GetResponse()

   at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)

The latest error I've managed to track down to one single line of code:

_setup.driver.FindElement(By.XPath("//button[@class='buttonSmall lockBookingButton']")).Click();

The annoying thing is, trying to fix the problem is proving difficult, as if I run the test on my local machine, in debug it passes. Additionally, if I run it via the NUNIT runner on the build machine I'm running the test off, it also passes. It only seems to fail as part of our automated build running process when using Teamcity. Like I said, this has been running fine for months previously, and the only thing that has changed is the selenium webdriver kit.

I have experienced this problem before, whilst in debug, and when a Click() line of code was called, Firefox appeared to lock up, and only stopping the test would allow Firefox to continue. There are a number of suggestions on here including modifying the webdriver source? I'd like to not go down that route if possible if anyone else can offer any suggestions.

new FirefoxDriver(new FirefoxBinary(),new FirefoxProfile(),TimeSpan.FromSeconds(180));

Launch your browser using the above lines of code. It worked for me.

I had a similar issue using the Chrome driver (v2.23) / running the tests thru TeamCity. I was able to fix the issue by adding the "no-sandbox" flag to the Chrome options:

var options = new ChromeOptions();

options.AddArgument("no-sandbox");

I'm not sure if there is a similar option for the FF driver. From what I understand the issue has something to do with TeamCity running Selenium under the SYSTEM account.

I first encountered this issue months ago (also on the click() command), and it has been an issue for me ever since. It seems to be some sort of problem with the .NET Selenium bindings. This blog post by the guy that works on the IE driver is helpful in explaining what's happening:

http://jimevansmusic.blogspot.com/2012/11/net-bindings-whaddaymean-no-response.html

Unfortunately, there doesn't seem to be a real solution to this problem. Whenever this issue has been raised to the Selenium developers (see here), this is a typical response:

We need a reproducible scenario, that must include a sample page or a link to a public site's page where the issue can be reproduced.

If you are able to submit a consistently reproducible test case, that could be very helpful in putting this bug to rest for good.

That said, perhaps you can try this workaround in the meantime. If the HTML button that you are trying to click() has an onclick attribute which contains Javascript, consider using a JavascriptExecutor to execute that code directly, rather than calling the click() command. I found that executing the onclick Javascript directly allows some of my tests to pass.

In my case, my button's type is submit not button and I change the Click to Sumbit then every work good. Something like below,

from driver.FindElement(By.Id("btnLogin")).Click();

to driver.FindElement(By.Id("btnLogin")).Submit();

BTW, I have been tried all the answer in this post but not work for me.

Got similar issue. Try to set more time in driver's constructor - add eg.

var timespan = TimeSpan.FromMinutes(3);



var driver = new FirefoxDriver(binary, profile, timeSpan);