Why does Selenium / Jenkins report two different ChromeDriver versions? - selenium

When I run Selenium jobs through Jenkins, I see 2 different ChromeDriver versions reported:
Expected
17:00:29.375 [TestNG-test=wsc tests-3] WARN c.r.a.p.c.c.CreditApplicationPage - Unable to locate field: {}
org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//form[#name='creditAppDynaValidatorActionForm']//span[#class='message']"}
(Session info: chrome=71.0.3578.98)
(Driver info: chromedriver=2.45.615279 (12b89733300bd268cff3b78fc76cb8f3a7cc44e5),platform=Linux 3.10.0-693.11.1.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'jenkins-slave-4368551bbabf', ip: '172.17.45.11', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-693.11.1.el7.x86_64', java.version: '1.8.0_152'
The Driver info: chromedriver=2.45.615279 makes sense to me. This is the driver version we've installed.
Alternate
org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"//form[#name='creditAppDynaValidatorActionForm']//span[#class='message']"}
(Session info: chrome=71.0.3578.98)
(Driver info: chromedriver=70.0.3538.67 (9ab0cfab84ded083718d3a4ff830726efd38869f),platform=Windows NT 10.0.17134 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
For documentation on this error, please visit: https://www.seleniumhq.org/exceptions/no_such_element.html
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'jenkins-slave-4368551bbabf', ip: '172.17.45.11', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-693.11.1.el7.x86_64', java.version: '1.8.0_152'
What does the Driver info: chromedriver=70.0.3538.67 mean; why is it displayed here? Version 70.0 is so very far off from 2.45.

A colleague pointed me to the answer:
The driver version reported is the WebDriver version as run through the Selenium Grid.

Related

org.openqa.selenium.WebDriverException: unknown error: session deleted because of page crash

I am getting thw following error while running the code headless on a server.
I have also incorporated the following two ways:
chromeOptions.addArguments("--disable-dev-shm-usage");
chromeOptions.addArguments("--no-sandbox");
Still no success.
Error:
org.openqa.selenium.WebDriverException: unknown error: session deleted because of page crash
from unknown error: cannot determine loading status
from tab crashed
(Session info: headless chrome=83.0.4103.116)
Build info: version: '3.14.0', revision: 'aacccce0', time: '2018-08-02T20:19:58.91Z'
System info: host: 's2c-beta-app', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-1121-aws', java.version: '1.8.0_275'
Driver info: org.openqa.selenium.chrome.ChromeDriver
How can I resolve this error?

selenium TimeoutException on Linux/ chromium

I am getting a timeout error on the linux using chromium browser but same is working on the windows.
I am using the serenity BDD.
Caused by: org.openqa.selenium.TimeoutException: Expected condition failed: waiting for TransactionPage.moreTransactionButton to be not displayed (tried for 5 second(s) with 100 milliseconds interval)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'mesos-jenkins-9fd7a38e844041bcbcbf7079e094c3bc-java180u161-mave', ip: '172.17.0.3', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-693.11.6.el7.x86_64', java.version: '1.8.0_161'
Driver info: driver.version: unknown
at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:304)
This is button I am waiting for to get invisible.
#FindBy(xpath = "//button[contains(.,'Show More Transactions')]", timeoutInSeconds = "180")
public WebElementFacade moreTransactionButton;
Edit 1:
This is the waiting function
element(moreTransactionButton).waitUntilNotVisible().withTimeoutOf(Duration.ofSeconds(300));

Unable to open Chrome browser using selenium 3.10.0

I am using following configuration:
Windows 7
Java: 1.8.0_91
Selenium: 3.10.0
Chrome browser: 62.0
Chrome Driver : 2.34
While running found below error:
org.openqa.selenium.SessionNotCreatedException: session not created exception
from disconnected: unable to connect to renderer
(Session info: chrome=62.0.3202.62)
(Driver info: chromedriver=2.34.522940 (1a76f96f66e3ca7b8e57d503b4dd3bccfba87af1),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 938 milliseconds
Build info: version: '3.10.0', revision: '176b4a9', time: '2018-03-02T19:03:16.397Z'
System info: host: 'OFFICE-PC', ip: '192.168.1.230', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_91'
Driver info: driver.version: ChromeDriver
Hmmmmm... Looks familiar.
Have you checked that you are not using a 32bit ChromeDriver for a 64bit Chrome browser?

Unable to launch Firefox browser in Windows Xp (32 bit) Using Selenium Webdriver

I am unable to launch the firefox browser (49 version) and with Selenium Jar is 2.5.3 .
Getting Below error:-
*2016-11-10 18:45:36 ERROR BrowserConfig:293 - Error in EbselenCore.setBrowser:Specified firefox binary location does not exist or is not a real file: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
Build info: version: '2.53.0', revision: '35ae25b1534ae328c771e0856c93e187490ca824', time: '2016-03-15 10:43:46'
System info: host: 'karthik', ip: '0.0.0.0xx', os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version: '1.8.0_111'
Driver info: driver.version: unknown*
Even i tried with the system.setproperty to the
System.setProperty("webdriver.firefox.bin", "xxxxx\\xxx\\firefox.exe");
System.setProperty("webdriver.chrome.driver", "xxxxx\\xxx\\chromedriver.exe");
System.setProperty("webdriver.chrome.bin", "xxxxx\\xxx\\chrome.exe");
Even i tried with the chrome driver :-
Nov 11, 2016 2:29:10 PM org.openqa.selenium.os.UnixProcess checkForErrorSEVERE: org.apache.commons.exec.ExecuteException:Process exited with an error: -1073741511 (Exit value: -1073741511) 2016-11-11 14:29:11 ERROR BrowserConfig:293 - Error in EbselenCore.setBrowser:Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. Build info: version: '2.53.0', revision: '35ae25b1534ae328c771e0856c93e187490ca824', time: '2016-03-15 10:43:46' System info: host: 'karthik', ip: 'x.x.x.x.', os.name: 'Windows XP', os.arch: 'x86', os.version: '5.1', java.version: '1.8.0_111' Driver info: driver.version: SeleniumChromeDriver
Thanks in advance for your response.
Selenium 2.5.3 only work with firefox 46 and older. You need to use selenium 3 and newer from firefox 47 onwards. You also need to use geckodriver.

Unable to work with Chrome browser using Selenium webdriver in codeception

Starting selenium + chrome driver with this is command
java -Dwebdriver.chrome.driver=chromedriver.exe -jar selenium.jar
It start the server
This is my acceptance.suite.yml file
class_name: AcceptanceTester
modules:
enabled:
- WebDriver:
url: ''
browser: chrome
window_size: 1280x768
curl:
CURLOPT_TIMEOUT: 60
This is what i am receiving as error when i try to execute the test case
[Facebook\WebDriver\Exception\UnknownServerException]
unknown error: cannot parse capability: proxy
from unknown error: must be a dictionary
(Driver info: chromedriver=2.21.371459 (36d3d07f660ff2bc1bf28a75d1cdabed0983e7c4),platform=Windows NT 6.2 x86_64) (WARNING: The server d
id not provide any stacktrace information)
Command duration or timeout: 518 milliseconds
Build info: version: '2.52.0', revision: '4c2593c', time: '2016-02-11 19:06:42'
System info: host: 'FR301-216', ip: '172.16.102.106', os.name: 'Windows 8', os.arch: 'amd64', os.version: '6.2', java.version: '1.8.0_65'
Driver info: org.openqa.selenium.chrome.ChromeDriver
This is an existing bug in the new codeception version (2.1.5 and above). The solution is to downgrade your codeception version to 2.1.4.