I'm running an automated test in Firefox browser using Selenium Web Driver and TestNG, but I'm encountering this error:
org.openqa.selenium.internal.seleniumemulation.WaitForPageToLoad handleSeleneseCommand
WARNING: Cannot determine whether page supports ready state. Abandoning wait.
This has only recently been occurring, so I think it might have to do with Firefox updates. Does anyone know what might be causing this issue?
Related
Has anyone seen the issue when debugging an Asp.Net 5 (core) application where the application seems to just go to sleep. Selecting another function/page in the browser just says "Waiting for LocalHost" (as I am running it locally on IIS Express).
We have a staged version of the Asp.Net app and it has no such problem. It runs wonderfully, but in Debug mode, it can have serious delay issues in executing code. Nothing is reported in the output window, during the time it appears to be doing nothing. Nothing on the Diagnostic tools windows either
A lot of the time - it will ultimately come back if you let it do its thing. But sometimes it can take up to 15-30 seconds.
The issue seems to become more prevalent when you change the Razor or javascript client files while the app is running?
Soemtimes pressing F5 on the web page makes it get out of its sleep mode (but not always, and it seems the more times you do this it, the slower it gets). Is it perhaps rebuilding the page that changed? but why the delay?
Again this works fine in Staging or Production (as none of the back end client side files would be changing). But it can be very annoying
Any ideas?
For me it was my Anti Virus. As soon as I disable AVG all requests get immediately run by the debugger.
So I found I didn't have the web tool extensions even installed - and after I installed it - the Freeze disappeared, but a colleague of mine still has the problem (as he already had the extension loaded and there is no way to uninstall it once its loaded
USING:
currently latest Protractor 3.3.0
Firefox is 45
Mac OS X Yosemite
ISSUE:
So I've been trying to figure out when this slowness occurred. Pretty much everything is running very slow. I have a login page that used to take around 5 seconds now it's taking almost 3 times longer.
WHAT I'VE TRIED
I did find a setting that seemed to make things work like how I expected them to work for the login page but then it messes things up on other tests because it's not waiting long enough.
the only way i've been able to speed it up was the setting mentioned above
exports.config.capabilities.pageLoadingStrategy = "eager";
I have tried via browser stack on firefox 45 and on windows 7 and mac osx Yosemite but the problem seems to be there still. I also tried reverting to protractor 3.0 and 2.51 to see if that made a difference. I tried using older firefox browsers like 43 and 44. I can't seem to find much on the issue. I don't know if it's possible to somehow set the pageLoadingStrategy to eager and then once logged in back to normal? Any suggestions on how to speed up firefox are appreciated.
Firefox takes almost 3 times longer than chrome.
CHROME
FIREFOX
It looks like you are running Chrome with directConnect and Firefox without.
You can avoid starting up the selenium server and run Firefox in directConnect too:
directConnect: true - Your test script communicates directly Chrome Driver or Firefox Driver, bypassing any Selenium Server.
The advantage of directly connecting to browser drivers is that your test scripts may start up and run faster.
If I use firefox directConnect: true.
Then browser.action() is not working. It give error Http method not allowed
I am having a problem whereby running a test using selenium webdriver in firefox starts the firefox browser with firefox webdriver disabled as shown below.
Because of this the test times out with the error
org.openqa.selenium.WebDriverException: Failed to connect to binary
FirefoxBinary(C:\Program Files\Mozilla Firefox\firefox.exe) on port 7055; process output follows:
If I quickly enable the webdriver and restart the browser the test manages to run and complete itself so I'm guessing the problem is just that this add-on starts disabled when running a test.
How can I remedy this? Thanks!
Check the version of Selenium and FireFox you're using. Incompatible versions can result in these kinds of problems. See: Where can I find a definitive Selenium WebDriver to Firefox Compatibility Matrix?
Unfortunately the only option at the moment is to use Marionette WebDriver
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Marionette/WebDriver
That works for Selenium 3 WebDriver tests. However if you use some framework on top of this you should check its roadmap to get information on when "geckodriver" or Marionette is going to be supported there.
Most likely the easiest approach to solve the issue in question for now is to downgrade browser (e.g. to Firefox 46) and use FireFox driver.
Try remove the extension completely. Normally Seleniums FirefoxDriver is enough to start your test.
WebDriver driver = new FirefoxDriver();
This should work without any external Firefox Plugins.
We have existing selenium tests in many projects but these were turned off
due to problems running selenium on the server. Selenium has been updated
a few times since then but it may be that the underlying problem is that
we were continually re-launching firefox.
i want to know if there is any other browser which i can keep running at backend and no need to open every time which sometime slow the server and at worse hang it.
please suggest some solutions.
I am not sure if I can remote debug an application running on an Iphone which is not next to me? We test your app. well but some users have issues sometimes we can not replicate and dont know where to start digging in this cases. So it would be very easy for us when we can just connect the remote debugger via the internet to an device. Is is possible somehow?
Most of the guys using the app we could remote to there PCs (but the majority dont uses macs...) and run tools there, is this maybe an easier solution?
For Mac Os I found this http://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/XcodeDebugging/300-Debugging_Programs_Remotely/remote_debugging.html
But this is not for iOS...
Thx very very much already
Our company just released a service exactly for that purpose: http://apphance.com . It allows you to very easily (5 minutes) integrate your application - add framework project basically and you get all the remote debugging capability included (you can access everything from very nice web panel):
You can see logs of running application (in near-real-time)
You can see how device conditions change over time (rotation, wifi/gprs, battery, others)
You get crashes reported to you automatically with all relevant information
Even out-of-memory errors are reported
Your testers can even report problems by shaking the device - including automated screenshots
and more.....
It's currently, closed beta stage but you can request access and for sure you get it.
All you need to do is get the crash log(you can get this at any time through the Xcode Organizer or iTunes Connect in released Applications) symbolicate it and ask the tester what they did to cause the error. This will give you every piece of info you could of gotten from GDB.
Check out https://testflightapp.com/sdk/, you can get crash reports, remote logs, see how is the teststing going and much more, see link for further details.