My scripts are not running with firefox and I am using firefox version-49.0.1, Here is the error Selenium::WebDriver::Error::WebDriverError: unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055).
Downgrade your Firefox to 47.0.1 and try again.
Downgrade is an oppertunity but if you want to be sure that your tests run with the newest version of Firefox, you can run the Selenium-RC server look here.
In my case this fixed many compatibility issues. This works with every Firefox, Google Chrome and Internet Explorer version so far. Hower in my opinion your whole project would be ordered better.
Related
I have a jmx file where i have written selenium code with javascript. I am unable to run it in EC2 using JMeter.
Here is the error message.
unknown error chrome failed to start exited abnormally
Chrome failed to start
Looking into the log file it appears you're using ChromeDriver 2.20. It is quite an outdated version which supports Chrome (or Chromium) versions 43-48.
If you are using a newer Chrome - you have 2 options:
Upgrade to ChromeDriver 2.29 which supports Chrome versions 56-58
Downgrade your Chrome browser to version 43-48
References:
ChromeDriver Release Notes
Getting started with ChromeDriver on Desktop
The WebDriver Sampler: Your Top 10 Questions Answered
It seems you don't have neither Chrome nor specific Chromedriver on your EC2 machine.
For the latter, get it there, then you're going to set system property webdriver.chrome.driver to the path to your driver (including the executable name).
As for installing conventional chrome on that GUI-less machine - I'm quite not sure it's going to work, but you may try.
Although the package is anyway out of standard AWS package repositories, so you'd be driven to do that manually from local package.
Let me know if that helped, please.
selenium.common.exceptions.WebDriverException: Message: Can't load the profile. Profile Dir: C:\Users\\AppData\Local\Temp\2\tmpc2_p3ubt If you specified a log_file in the FirefoxBinary constructor, check it for details.
When I try to run my Python script, Firefox is timing out. Does anyone have any suggestions on which versions i need to match?
Uninstall current firefox version than Download Firefox from this link https://ftp.mozilla.org/pub/firefox/releases/46.0.1/win64-EME-free/en-GB/Firefox%20Setup%2046.0.1.exe and then try again
Note : you have to uncheck automatic upgrade of firefox after install of 46 using below setps:
Goto Options
Goto advance
Under Firefox updates: Never check for updates (not recommended: security risk)
If you want to run on firefox >= 48 then you need to upgrade to selenium 3beta. https://seleniumhq.wordpress.com/2016/07/29/announcing-selenium-3-0-beta1/
It wont and its a known issue, Refer thread here
https://github.com/SeleniumHQ/selenium/issues/2559
Can't fix.
In Firefox 48, Mozilla requires extensions to be signed. They have
refused to sign Selenium's Firefox driver extension (webdriver.xpi).
Feel free to contact them and/or log an issue for them at
https://bugzilla.mozilla.org
The way forward now is to use GeckoDriver. Which is now the default
implementation used in 3.0-beta
This issue has been known as a long time coming, I highly recommend
pinning your automation to use Firefox 45 ESR until a release of using
GeckoDriver/marionette is stable enough for your tests.
Gecko Driver is a way forward.
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'm running some Robot Framework integration tests with Firefox 21.0 for Ubuntu. Recently my Firefox was updated and now it always pops up a prompt about incompatible add-ons when it starts. That's unacceptable, as then the tests cannot continue. The prompt looks like this:
There are several instructions about this on the web, but they are all either for some old version of Firefox or for some similar but not the same situation (like when Firefox asks whether to disable 3rd party plugins), or they require one to disable the compatibility check for each version of each add-on separately, so none of them seem to work. How do I get rid of the prompt for good?
Find the prefs.js file from your Firefox profile directory, then add this line into it:
user_pref("extensions.showMismatchUI", false);
Presto! No more warnings about incompatible add-ons.
After a recent upgrade to Firefox 4, all of my automated selenium tests seem to be hanging on the initial 'Launching Firefox...' command during testing.
Has anyone seen a fix for this, or is my best bet to downgrade?
Have you updated to Selenium 2.0b3? Earlier versions don't support FF4.
** EDIT* *
RC2 is now available:
http://code.google.com/p/selenium/downloads/list
I was having the same issue. 'Launching Firefox' command, a blank Firefox window opens and the test hangs. Looking at the Firefox Add-ons the three extensions that Selenium installs were all incompatible and disabled. Turns out my test was still accidentally starting up the wrong selenium version. Switching to 2.0b3 fixed the issue.
Recommend you to use latest version of selenium with firefox 4. for me it is working fine withoutany problem.
I am using :
Selenium Server : selenium-server-2.0b2
I hope it helps.