We have selenium tests in C# running on jenkins. With the latest version of Chrome 75 the tests are starting to fail during execution with the error "Chrome failed to start"
I went through some articles and have implemented the below code as part of my arguments for Chrome.
chromeOptions.AddArgument("--enable-automation");
chromeOptions.AddArgument("--no-sandbox");
chromeOptions.AddArgument("--disable-extensions");
chromeOptions.AddArgument("--disable-print-preview");
chromeOptions.AddArgument("--disable-gpu");
chromeOptions.AddArgument("--disable-software-rasterizer");
chromeOptions.AddArgument("--disable-gpu-sandbox");
chromeOptions.AddArgument("--disable-features=VizDisplayCompositor");
chromeOptions.AddArgument("--start-maximized");
chromeOptions.AddArgument("--disable-dev-shm-usage");
chromeOptions.PageLoadStrategy = PageLoadStrategy.Normal;
This happens during jenkins execution only.
I'm seeing this on Chrome 76. The solution seems to be to remove the --disable-software-rasterizer argument.
Related
Recently, we've started to get these kind of warnings on the console when running Protractor tests:
[12252:14584:1207/223118.187:ERROR:process_metrics.cc(105)] NOT IMPLEMENTED
[12252:14584:1207/223118.187:ERROR:process_metrics.cc(105)] NOT IMPLEMENTED
[12252:14584:1207/223318.188:ERROR:process_metrics.cc(105)] NOT IMPLEMENTED
It feels like they happen randomly but doesn't affect the test execution.
The only problem is that they pollute the output console making it more difficult to keep track of tests being executed and test results reported by jasmine/protractor.
Is there a way to turn off this kind of chromedriver warnings?
Using Protractor 5.2.2, ChromeDriver 2.34.
We've found this --silent flag that can be passed to chromedriver executable, but could not find a way to configure protractor to pass this flag when launching chromedriver..
It seems to be an issue with chrome v63
https://github.com/SeleniumHQ/selenium/issues/5189#issuecomment-351605839
You should be able to pass the --silent flag to chromedriver in your conf file. Something like:
capabilities: {
browserName' : 'chrome',
'chromeOptions' : {
args: ['--silent']
}
}
}
"This warning message was generated by a bug in Chrome v63.
Upgrading to v64 (64.0.3282.167 as of this morning) resolves it."
I'm trying to run a test on google's website and when I send the text I'm saying the following message:
Missing 'text' parameter (IndexOutOfBounds)
Code:
browser.FindElement(By.Name("q")).SendKeys("a");
What I do not understand is that until yesterday the code was running normally.
Can someone help me solve this error?
tks!
Version:
geckodriver-v0.16.0-win64
Selenium Client & WebDriver - C# 3.4.0
Firefox 53.0v
Try updating your Selenium.WebDriver and Selenium.Support packages to latest (v3.4.0). If you already have v3.4.0 make sure you have rebuilt all.
I just hit the same issue and updated v3.2.0 -> v3.4.0 and that fixed it for me.
(Just for context, I ended up with that error after getting 'Expected [object Undefined] undefined to be a string (IndexOutOfBounds)' following an automatic Firefox update to v53. The fix for that was to upgrade to geckodriver v0.16.0)
#Kayh and #NickBaker
There is still an issue: how did that work?
https://github.com/mozilla/geckodriver/issues/511
I am using Firefox 53.0.3 (32-bit), geckodriver 0.16.1 to drive browser with Selenium 3.4.0 but still getting
System.InvalidOperationException : Missing 'text' parameter (IndexOutOfBounds)
EDIT:
https://github.com/mozilla/geckodriver/issues/511 fixed now on 02 July 2017. Combination of Selenium client binding 3.4.3, geckodriver 0.17, Firefox 54 works now.
I've encountered problems with starting JMeter and WebDriver Set.
I set - Thread Group with:
jp#gc FF Driver Config
jp#gc Web Driver Sampler
View Results in Table
In Web Driver Sampler I have following lines:
WDS.sampleResult.sampleStart()
WDS.browser.get('http://google.com')
WDS.sampleResult.sampleEnd()
And I get following error:
ERROR - jmeter.threads.JMeterThread: Test failed! java.lang.NoClassDefFoundError: Could not initialize class org.apache.http.conn.ssl.SSLConnectionSocketFactory
How can I make it work?
Make sure you use the latest JMeter version (2.13 as for the moment)
Make sure you use the latest WebDriver Set plugin package (1.3.1 as for now)
Make sure you use supported Firefox version
Supports native events for Firefox version 31 (immediately previous ESR).
Native event support has been discontinued for versions of Firefox later
than 33. Synthetic events tested on Firefox versions 31 (immediately
previous ESR), 38 (immediately previous release and current ESR), and 39
(current release).
Before starting JMeter:
go to JMeter's /lib folder
locate .jar files which names start with "http"
delete files which have lesser versions
If you still experience problems check out The WebDriver Sampler: Your Top 10 Questions Answered guide
Hello All
I've discovered an issues, which I'm not sure it really is an known issue with the framework or it's due to the versions of Protractor + CucumberJS that I am using, these are:
"cucumber": "~0.7.0",
"protractor": "~2.5.1",
"selenium-standalone": "3.0.0",
I'm using this versions as of today, I know that CucumberJS was separate from Protractor, but since our current project is using Node < 4, I cannot update it.
Having said this, the error that I'm having is when I run the test suite with protractor config.js and the seleniumAddress attribute commented (it starts up a webdriver automatically at random port)
The error that appears, when the suite finishes is:
throw new Error('This driver instance does not have a valid session ID ' +
^
BUT when I run the exact same suite, starting webdriver manually and setting the selenium address, the test passes!!!
The suite contains:
17 scenarios (17 passed)
55 steps (55 passed)
Does anyone knows what could be the reason? My first thought is that starting the server manually it would make webDriver slower, and therefore test actions would be too, so... but I had compared both time executions and there's only 1 second difference between both....
I had realized, that the problem with all is that since I had commented out the seleniumAddress line, Protractor was starting up webDriber-manager automatically, and when I added the line and manually started WebDriver, the error did not happen again. NOT sure what's the matter with it starting up automatically but, in case you ran into the same problem here's the solution!
Thanks
I have the following in my selenium-webdriver test (the test is written as coffee-script):
#driver = new selenium.Builder()
.withCapabilities(selenium.Capabilities.chrome())
.build()
Yet when I run this test the error I get is:
Error: Failed to install profile; firefox terminated with Result(code=-1073
741819, signal=null)
I am perplexed why its trying to start firefox (there is no reference to firefox in my code). Also, at one point this was working. I am not sure what changed in my laptop which has resulted in this behavior.
Thanks for any help.