When the Mouse Over Keyword is called I get the following error :
WebDriverException: Message :POST /session/bcb99bc5-1b47-4438-b1b7-471785ea34c8/moveto did not match a known command on Mozilla FireFox(geckodriver)
Sadly this appears to be a bug in the Mozilla/geckodriver side of the Actions implementation that has been lingering since mid 2016. If you really need this, switch to something not Firefox or grab a pre-geckodriver Firefox (47 or below, I believe) and use the older webdriver bindings (i.e., Selenium 2). Unfortunately, it is not as easy as just getting the older FF version.
See :
[Bugzilla bug report][1]
[Gecko bug report][2]
https://bugzilla.mozilla.org/show_bug.cgi?id=1292178
https://github.com/mozilla/geckodriver/issues/159
**Question:**WebDriverException: Message :POST /session/bcb99bc5-1b47-4438-b1b7-471785ea34c8/moveto did not match a known command on Mozilla FireFox(geckodriver)
**Answer:**Selenium web driver should be updated version and Firefox latest version will not supports the old selenium web driver,Firefox version should be 49.0 and selenium web driver version should be 3.0,then that issue will not come while executing the script.
Related
Now, I am started to learn Selenium WebDriver.I have got the following error.
Exception in thread "main" java.lang.IllegalStateException: The path
to the driver executable must be set by the webdriver.gecko.driver
system property; for more information, see
https://github.com/mozilla/geckodriver. The latest version can be
downloaded from https://github.com/mozilla/geckodriver/releases.
Does anyone know how to resolve this error?
It seems like you are using latest version of selenium. Unlike older versions, wherein you don't need to set system property for browser driver executable in case of firefox, the System.setProperty("path to geckodriver.exe") is required to be mentioned in code.
This should resolve your issue
I am using Robot Framework for test automation.
Recently I upgraded my Chrome browser to the latest version, V 57.0
Since then, I am unable to execute my test scripts on Chrome.
The webpage opens up and navigates until Login page, the cursor focus is set on Username field and then it just keeps on trying for few seconds until i receive an error saying:
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on
failure: WebDriverException: Message: unknown error: cannot get
automation extension from unknown error: page could not be found:
chrome-extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html
(Session info: chrome=57.0.2987.133) (Driver info:
chromedriver=2.24.417431
(9aea000394714d2fbb20850021f6204f2256b9cf),platform=Windows NT
10.0.10586 x86_64)
I have no extensions installed in the browser.
Also followed up a similar post here
It just mentions about removing your extensions, which I already did.
Thanks
EDIT: Always make certain you are using current and compatible versions of Chromedriver. I always suspect this when the problems show up at the element level. The driver has to be updated a lot as the browser evolves. In your case, you've indicated a current Chromedriver is a solution. Note that this solution generalizes to all browsers.
If the problem were more related to window sizing/resizing, it might be due to the fact that selenium is trying to use an extension to perform a windowing function. Issues with running headless... This assumes you are running headless.
Solution is likely to rework the test for headless runs, or run else try a real browser.
Your chromedriver is not latest as said in your error message (Driver info: chromedriver=2.24.417431). Latest available chromedriver version is V2.28
Use latest available Chrome Drivers and you will be all good.
Mark +1 if this answer is useful to you.
I am getting the below exception while trying to connect a esx-i 5 machine using vijava vsphere API.
vijava is the VMware Infrastructure JAVA API.
I am using the VI Java API 5.5 Beta vijava55b20130927.
What might be the root cause of this issue.
java.rmi.RemoteException: VI SDK invoke exception:java.rmi.RemoteException: VI SDK invoke exception:org.dom4j.DocumentException: **Error on line 4 of document : Open quote is expected for attribute "{1}" associated with an element type "rel".** Nested exception: Open quote is expected for attribute "{1}" associated with an element type "rel".|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:131)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:1437)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:100)|
[12:02:07:318]|[12-18-2014]|[SYSOUT]|[INFO]|[135]|: at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:84)|
If you will switch to using YAVIJAVA I can help.
The Beta version of VIJAVA has a bug where only a RemoteException is ever thrown. That bug is fixed in YAVJAVA 5.5.08-DEVELOPMENT or newer which as of this comment is only available on github (older versions in maven have this bug)
YAVIJAVA includes logging via log4j and if you enable debug logging when you run the command you can even get the XML payloads that are coming and going from the server which I can use to help you trouble shoot this problem.
I came in to the office yesterday morning to find that my Capybara tests couldn't interact with Chrome. I'm seeing
Selenium::WebDriver::Error::UnknownError: unknown error: unable to discover open pages
Googling around revealed that this was likely caused by an out-of-date chromedriver or selenium-webdriver, which sounded very plausible, since neither had been updated in a long time (I think chromedriver was at 2.2 and selenium-webdriver was at 2.35.1), and since Chrome auto-updated to 32.0.1700.77 on January 14, that seemed like good solid evidence to me.
So I've updated selenium-webdriver to 2.39.0. Figuring out what version of chromedriver I had been using actually turned out to be more difficult. I had a version of chromedriver sitting in my Downloads directory that I thought my code was referring to, but I couldn't find my Downloads directory in the PATH (I'm using OS X by the way). I tried replacing this file with version 2.8 from here, but it had no effect. I became skeptical that the version in my Downloads directory was the version that was being used in the first place, so I used brew to install it. brew info chromedriver now yields:
chromedriver: stable 2.8
http://code.google.com/p/chromedriver/
/usr/local/Cellar/chromedriver/2.8 (2 files, 21M) *
Built from source
From: https://github.com/Homebrew/homebrew/commits/master/Library/Formula/chromedriver.rb
Looks good. My PATH contains /usr/local/bin, which has a chromedriver link to the location brew installed to. As far as I understand it, this should allow my automation to detect and launch the chromedriver.
Unfortunately, my issue is still unresolved. I remain unable to discover pages. Can anyone confirm that I've done what one normally does to set up the chromedriver?
Side Question: After downloading chromedriver 2.8 directly and also installing it with brew, I tried launching both the downloaded version and the brew version separately to confirm that either version could launch successfully. I'm certain they are both in fact version 2.8, but when I launch either one the console says:
Starting ChromeDriver (v2.2) on port 9515
Is that normal? I certainly wasn't expecting it to say v2.2, but there are no other versions apart from 2.8 installed by brew (so I doubt brew is accidentally using the older version), and when I run the file I downloaded directly, I'm quite sure it's version 2.8 from the Chromedriver website. Is this an oversight on their part, or does v2.2 refer to something else, unlikely though that may seem?
It would be tricky to verify the chrome driver version frequently when you download it with homebrew. I would suggest downloading the driver and maintaining it in a folder mapped in your PATH.
So that maintaining or identifying the driver version will be easy with the below steps:
Go to the folder where you have chromeDriver
Open command prompt pointing the folder
run: chromeDriver -v
ChromeDriver is at version 2.16 now. I would recommend manually updating your driver instead of updating with whatever older version that homebrew wants to update you to.
You can use command line: pip freeze to list down all packages you have installed with their version.
Or you also can use pip show <package name> to check the details of the package, which also includes package version.
Click here
chrome driver version
for checking your chrome driver version.
Now it's time to check the latest release version. So click here latest release version
Compare between;
I know that there is documentation on the ghostdriver wiki on how to attach it to a selenium grid. For those that don't know you can find it here
I've compiled the special phantomjs twice, tried to attach it to selenium servers local, and remote using both Selenium versions 2.24 and 2.25 to no avail. It starts up Ghostdriver locally just like you expect, but there's certainly no registering going on.
I tried both ip/localhost:4444 and ip/localhost:4444/grid/register with no results. I also thought perhaps it just didn't show up on the grid console and tried to run tests against it anyway, which failed stating there was nothing populating the grid.
I've tried this on both CentOS 6 and Ubuntu 12.04 with no luck.
I'm out of ideas. Has anyone else had problems like this?
I had exactly the same problem and fixed it with using the lastest version of selenium-grid.
The good website: https://code.google.com/p/selenium/wiki/Grid2 (this is no longer http://selenium-grid.seleniumhq.org/).
Here the steps (version 2.31.0):
Download the selenium-server:
wget https://selenium.googlecode.com/files/selenium-server-standalone-2.31.0.jar
Launch selenium grid server:
java -jar selenium-server-standalone-2.31.0.jar -role hub
In a new terminal, launch GhostDriver:
phantomjs --webdriver=5555 --webdriver-selenium-grid-hub=http://localhost:4444
Check out available remote control on http://localhost:4444/grid/console.
You should see something like that:
listening on http://127.0.0.1:5555
test session time out after 300 sec.
Supports up to 1 concurrent tests from:
phantomjs
I was testing this commands on CentOS 6.3, I hope it works for you!