My test cases were working fine with selenium+chrome 23. I upgraded to chrome browser 24 and tried running the cases. although selenium executes the cases, the changes are not reflected in UI sometimes. I am using chrome driver 26 and selenium webdriver 2.29.
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.
Errors:
[6944:3028:0128/220426:ERROR:chrome_views_delegate.cc(176)] NOT IMPLEMENTED
[6944:3028:0128/220426:ERROR:desktop_root_window_host_win.cc(746)] NOT IMPLEMENT
ED
[6944:3028:0128/220430:ERROR:desktop_root_window_host_win.cc(746)] NOT IMPLEMENT
Read that the problem is in versions of Google Chrome and chromedriver.exe but I have the last version of Google Chrome - 32.0.1700.102 m and chromedriver.exe - 2.8.
Test runs fine.
That's just the console output from ChromeDriver, which does't indicate anything wrong with the tests. You can silence these outputs in order to avoid them on the console. Refer this link: Silencing Chrome driver console outputs when I run my tests.
I'm using Selenium to automate Google Chrome to take screenshots. And I use Task Scheduler to run this application automatically at specified time daily.
The problem is that the screenshots taken is blank/black. However, if I manually run this app by double click its icon, the screenshots gotten is good.
The version of Selenium and Google Chrome I used is all the latest stable. Selenium 2.35 and Google Chrome 29. And I am using C# bindings.
Anyone knows what's wrong with Task Scheduler and how to fix this blank/black screenshot issue?
Is it possible that you recently update the version of your Selenium? The ChromeDriver 2.x has an issue with blank screenshots: https://code.google.com/p/chromedriver/issues/detail?id=309.
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