I have an integration test suite that uses selenium along with chromedriver. Within the last week, I have noticed that the aw snap page from chrome has shown up very frequently. When I switch the chromedriver to firefoxdriver, everything works fine. What could be the cause of this outbreak of aw snap pages?
I am running with the latest version of Chrome and ChromeDriver:
chrome version 22.0.1229.79 m
chromedriver_win_23.0.1240.0
Related
I'm working on functional testing. I'm using selenium, protractor and cucumber with Typescript. I'm generally testing on Chrome.
Recently, I've got a problem with my Chrome webdriver (See the image below).
Rendering problem on Chromedriver
As you can see, it seems to be a rendering problem. The problem occurs only when I'm running chrome with selenium webdriver and it triggers with all of my applications.
Environment :
MacOS High Sierra
Protractor 5.3.2
Webdriver-manager 12.0.6
ChromeDriver 2.40
Moreover, my colleague who has the same environment and the same projects work perfectly on his machine.
I tried some tricks :
uninstall and install Google Chrome
downgrade chrome version
downgrade chrome driver version
Restart my machine and my environment
Clean the Chrome webdriver cache
Delete and redownload Node modules
Pull an ancient version of each project
Downgrading and upgrading Protractor
The rendering is working perfectly on Firefox, so the problem is on Chrome only.
By the way, all the page components are in the DOM, it is just about a display problem.
Is anyone got any idea ?
Does wct config allow for choosing a specific version of Chrome, like Chrome 34?
It seems to install chrome at the beginning every time I run wtc.
Following Polymer Documentation, it's possible to run tests choosing a browser installed on your computer. If you have Chrome 34 version and you execute test -l chrome, tests will run with this version. If you don't have Chrome 34, it's no possible.
All supported browsers to run tests are aurora, canary, chrome, firefox and ie.
Web Component Tester automatically finds all of the browsers installed
on your system and runs your tests against each one. If you wanted to
run your tests against a single browser, say Google Chrome, you could
polymer test -l chrome.
My Chrome automatically updated itself to Version 46.0.2490.71 (64-bit) today 10/14/15, and it looks like the developer tool is broken – it can not be launched.
I uninstalled Chrome latest, and installed Version 45, the developer tool is working fine. But then Chrome immediately upgrades itself to Version 46 again.
I tried to stop the auto upgrade of Chrome by: defaults write com.google.Keystone.Agent checkInterval 0
that does not seem to have any effect – Chrome still tried to auto-upgrade itself.
Is there anyone else using Chrome latest and have the same issue?
I am trying to run tests in Chrome browser 32.0.1700.76 (latest) using Selenium 2 Webdriver with chromedriver version 2.4
Chrome starts but the string "data;" is displayed in the url bar.
Those test worked fine with a previous Chrome version (28.xxxxx) but I can't downgrade Chrome.
Can anyone suggest me how can I solve the problem?
You need to either upgrade the ChromeDriver you are using or find a way to downgrade Chrome.
The basic principle of the issue is that the ChromeDriver v2.4's support of the most recent versions of Chrome is non-existent.
You get similar issues with Firefox, an upgrade will sometimes break the tests.
After Chrome's last release (Version 29.0.1547.66 m) chromedriver cannot find the new chrome alerts. For the previous versions everything worked fine. I also updated the selenium version to 2.9.0 and nothing changed.
Does someone else have the same issue?
Does it have to do with chrome version or selenium version?