Recently I switched my cucumber tests from capybara-webkit to chrome. Every time I am running tests locally a new chrome icon appears in the Deck bar. But 5th icon disappears when I start a new test (eg I see maximum four chrome icons)
I use
ChromeDriver 2.43.600229 (3fae4d0cda5334b4f533bede5a4787f7b832d052)
chrome Version 70.0.3538.110 (Official Build) (64-bit)
Gem versions:
selenium-webdriver (3.141.0)
capybara (3.11.1)
My capybara driver set up:
# features/support/env.rb
require 'selenium-webdriver'
Capybara.register_driver :chrome do |app|
options = Selenium::WebDriver::Chrome::Options.new(args: %w[no-sandbox])
options.headless! if tddium?
Capybara::Selenium::Driver.new(app, browser: :chrome, options: options)
end
Capybara.javascript_driver = :chrome
When I am running tests in the headless mode I see that new chrome icons appear, but I don't see browser window
How can I fix that?
Related
I have issue with running tests in headless mode with chrome options.
ChromeOptions options = new ChromeOptions(); options.addArguments("--headless"); driver = new ChromeDriver(options);
In UI mode test is executed fast(4seconds), but when I enable headless mode (40 seconds)
Headless mode:
UI mode:
Is there any other way to use chrome headless, whether something is changed in the mean time in driver itself? I have tried with different java, browser version and chrome driver and issue is the same..
Selenium 4.3.0, TestNG 7.4.0
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 ?
I am using Chrome Mobile Web Emulation.
Issue:
After updating chrome and chromedriver, click functionality is stopped working.
Stack-trace:
Not available, no exception or error is thrown.
Chrome version: Version 67.0.3396.62 (Official Build).
ChromeDriver: Version 2.39
Selenium: Version 3.12.0
Issue resolved after updating Chromedriver to 2.40.
They provide a version upgrade patch 2.40, just 7 day after releasing 2.39 version.
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.
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