I need help running Katalon studio with Chrome portable.
I am using ChromeDriver 75.0.3770.90 and Chrome Portable Version 75.0.3770.100 which I downloaded from portableapps.com
I have configured Katalon studio to use the portable version as seen in the screenshot below:
When I run the Katalon tests or try to record, the webdriver throws the following error:
Caused by: org.openqa.selenium.WebDriverException: unknown error: Failed to create a Chrome process.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'JHBPWM467086', ip: '10.110.43.144', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_181'
Driver info: driver.version: CChromeDriver
I have tried running Katalon as an admin and I have tried different supported Chrome drivers and I get the same error.
Is it possible to use Katalon with portable chrome ? If so, what configuration items am I missing to get it working ?
Thank you in advance for any help. Please let me know if I can clarify anything.
Katalon is unable to find the browser. You will need to set path to chromedriver manually:
System.setProperty("webdriver.chrome.driver", "path-to\chromedriver.exe")
Related
I don't know exactly how to replicate this error, but I do a lot of screenshots of the pages with WebDriver. Sometimes, suddenly I get this exception:
org.openqa.selenium.WebDriverException: java.net.ConnectException: Failed to connect to localhost/0:0:0:0:0:0:0:1:9958
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: '*******-*******', ip: '***.***.*.**', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '11.0.1'
Driver info: driver.version: ExtendedWebDriver
at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:92)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:285)
at org.openqa.selenium.remote.RemoteWebElement.getScreenshotAs(RemoteWebElement.java:392)
...
I don't quit/close the driver before that happens, and previous commands right before getScreenshotAs work as expected. It only happens with getScreenshotAs command. Never had this problem with any other. It's very rare though. I had this error maybe 20-30 in total. For example I run tests all night, then in 3 nights I get this error once.
Is this a known issue? I'm using ChromeDriver most of the times.
I didn't specify any related code, because it happens regardless. I use stock version of ChromeDriver and selenium java library both version 3.141.59.
I am not able to launch the Notepad.exe via windows application driver with selenium and Appium
Below are the versions of all
**Appium** : 1.15.1
**Selenium Standalone** : 3.141.59
**Java Client** : 7.2.0
I am starting Windows application driver server like this WinAppDriver.exe 4727.
I have tried this using testng and junit both,but getting the same error again and again.
Error Message is below :
org.openqa.selenium.WebDriverException: It is impossible to create a
new session because 'createSession' which takes HttpClient,
InputStream and long was not found or it is not accessible Build info:
version: '3.12.0', revision: '7c6e0b3', time:
'2018-05-08T14:04:26.12Z' System info: host: 'DESKTOP-0TL6S7C', ip:
'172.18.2.139', os.name: 'Windows 10', os.arch: 'amd64', os.version:
'10.0', java.version: '1.8.0_221' Driver info: driver.version:
WindowsDriver
You mentioned in the question about using Selenium Standalone v3.141.59 but as per the error trace logs:
Build info: version: '3.12.0', revision: '7c6e0b3', time: '2018-05-08T14:04:26.12Z'
Which is almost 2 years old.
Upgrading your build with Selenium Standalone v3.141.59 will solve the issue.
I am currently running some Protractor tests against Firefox and I am running into some issues concerning the Actions API.
Right clicking using the following does not work anymore:
browser.actions().click(protractor.Button.RIGHT).perform()
Protractor returns:
Failed: sendKeysToActiveElement
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: '****', ip: '****', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.14.1', java.version: '1.8.0_181'
Driver info: driver.version: unknown
I found out that the Actions API is deprecated in favour of the W3C standard. I am all for following standards but I am currently blocked by this. It seems that Selenium v4.0.0-alpha fixes this issue but as Protractor still relies on an older version, I cannot seem to make this work.
So I am looking for a workaround. I already tried the protractor-firefox-support package, but that doesn't work either.
Does anybody have a suggestion on how I can make this work?
Thanks in advance.
Cheers
I had similar problems with angular-material components and solved it by adding dispatchEvent method.
Try it out. Here is example of its usage.
I'm so confusing with this problem. So anyone who has taken the same trouble like this, please kindly inform me.
[Facebook\WebDriver\Exception\UnknownServerException]
Error communicating with the remote browser. It may have died.
Build info: version: '2.47.1', revision: '411b314', time: '2015-07-30 03:03
:16'
System info: host: 'DESKTOP-KLV8HD0', ip: '192.168.2.168', os.name: 'Window
s 10', os.arch: 'x86', os.version: '10.0', java.version: '1.8.0_144'
Driver info: driver.version: RemoteWebDriver
How to resolve ? Here is the description of application that I used:
Google Chrome (62.0.3202.75) -> Updated new version for now
Chrome Driver (2.9) -> Updated by http://chromedriver.storage.googleapis.com/index.html (I thought 2.9 version is newer version)
selenium-server-standalone-2.47.1
im trying to get a bunch of selenium tests to work on my Jenkins. Its an Ubuntu machine and i installed Chromedriver Chromium and xvfb.
After some problems it seems like its finding my chromedriver and the xfvb now but i still cant get any tests to run. They work fine local but now on Jenkins it says :
Fehlermeldung
Timed out after 5 seconds waiting for visibility of element located by By.xpath: //*[#id='loginForm-loginUsernameInput']
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-39-generic', java.version: '1.7.0_67'
Driver info: driver.version: unknown
Stacktrace
org.openqa.selenium.TimeoutException: Timed out after 5 seconds waiting for visibility of element located by By.xpath: //*[#id='loginForm-loginUsernameInput']
Build info: version: '2.25.0', revision: '17482', time: '2012-07-18 21:09:54'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '3.13.0-39-generic', java.version: '1.7.0_67'
Driver info: driver.version: unknown
at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:255)
at org.openqa.selenium.support.ui.FluentWait.timeoutException(FluentWait.java:270)
at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:222)
Im wondering why it doesnt show the chromedriver Version? Like version unknown? Im running the xvfb and the chromedriver in the background and im not using Jenkins to start it. I tried it with letting Jenkins start chromedriver and set the path -Dwebdriver.chrome.path=
but that results in the same error. Does anyone have a idea about this? I tried quite a few things but im still wondering if its the chromedriver that is not working or whats the Problem? Im using ChromeDriver v2.9.248304
You are using a very outdated version of Selenium. Typically, the newer Chrome versions might not work with older version of Selenium.
Try updating to Selenium version 2.44.0
I'm willing to bet this will fix your issue.