On Firefox 21, S-IDE worked fine. Just upgraded to the officially released FF22, and any test I try to run errors out:
[error] Unexpected Exception: fileName -> chrome://selenium-ide/content/selenium-core/scripts/htmlutils.js, lineNumber -> 309, columnNumber -> 8
Is there a workaround for this?
There's a fix now available, but you may encounter a similar problem with keyPress commands.
From what I have seen, the scripts stop on any 'Click' action when running FF22. Reverting back to FF21 is the best solution for now.
I upgraded to version 2.1.0 and all of old selenium jobs started to work fine. The official release for version 2.1.0 is on July fifth but it seems they have made it available probably because so many people are now having problems.
here is the link which has the version 2.1.0 available
http://docs.seleniumhq.org/download/
I posted the following issues with FF22 and Selenium IDE 2.0.. which you may also encounter.
https://support.mozilla.org/en-US/questions/963084
Related
So I've been having an issue getting my Protractor/Jasmine tests running in FireFox. I've been aware of the version issue from FireFox that doesn't support selenium angular/bootstrap etc etc and that has been my issue to date.
I was informed to try geckodriver but really can't find any good resources on how to set it up using protractor and jasmine. Or even which driver is the appropriate one to use.
Recently I've tried the following to get FF back up and running (all resulted with no luck):
Downgraded FireFox to as low as 33.x.x while keeping
Protractor/Jasmine at current versions (4.0.5 and 2.51 respectively).
Downgraded Protractor to as low as 3.0.0 while keeping FF at current version (47.0.1)
Downgraded both Protractor and FF to the lowest above versions.
Used Latest Version of FF 47.0.1 with lesser versions of Protractor.
Used Latest Version of FF 47.0.1 with latest version of Protractor 4.0.5
Used directConnect: true and directConnet: false
So I guess now I have one of two questions:
1. Could somebody post a protractor config snippet using the geckodriver / or direct me to a walk-through of this.
2. Inform me of a work around or a working solution (versions of both webdrivers/protractor/jasmine, etc).
If you need to see errors or my config file or anything at all please just simply comment and I'll be happy to revise.
There was a period of time around Firefox v46 and Selenium v2.5x where things were incompatible due to changes to the firefox web-driver. The issues were quickly addressed by the community.
The issue with Protractor lies with the webdriver-manager being a bit out of date with the updates. As per discussions on github, they are aware of this, and a fix is coming.
The workaround in the meantime is to manually update the outdated pieces.
Here's how you'd do it, run
webdriver-manager update
This will give you the paths to all the components the webdriver-manager handles for you.
Navigate to the selenium-server-standalone.jar file (protractor/node_modules/webdriver-manager/selenium/selenium-server-standalone-2.53.1.jar in my case) and replace this with the latest selenium standalone jar (anything v3+ should be good). Make sure to retain the exact filename as the previous jar file. (link: http://www.seleniumhq.org/download/)
Repeat the process to get the latest Gecko web-driver. Uncompress and replace the current version. (link: https://github.com/mozilla/geckodriver/releases)
Now run your tests through protractor and you should be good with the latest version of Firefox.
Good luck and happy testing :)
I have been tasked with fixing a bug found in a legacy app written in version 2.4.0 or 2.6.0 of STS.
After spending the better part of 2 days trying to port it to 3.6.2 without success I need to get my hands on either of these older releases to see if this even works or if there is something wrong with the app code base. I have spent the better part of an hour searching STS Spring for previous versions but can't find anything on the site. Where are previous versions of STS or why have they been stashed away?
OS Target: Window 7 - 64 bit
Thanks
Having a look at this post and the filename of the current version, you come up with: http://download.springsource.com/release/STS/2.6.0.SR1/dist/e3.6/springsource-tool-suite-2.6.0.SR1-e3.6.2-win32-x86_64.zip
Very strange that they are not linking the old versions even though they are still available.
I'm developing a plugin for Eclipse Juno under Mountain Lion.
I can test my plugin without problem by doing run as > Eclipse application.
However when I try to export the plugin by doing the following action it fails.
Open plugin.xml
Go to the tab Overview
Select Export Wizard
It returns the following error:
/Users/luca/Documents/University/PhD/FODA/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/compile.org.eclipse.pde.container.feature.xml:4: The following error occurred while executing this line:
/Users/luca/Documents/University/PhD/FODA/it.unibg.robotics.featuremodels.model/build.xml:31: /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/Classes does not exist.
The following error occurred while executing this line:
/Users/luca/Documents/University/PhD/FODA/it.unibg.robotics.featuremodels.model/build.xml:31: /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/Classes does not exist.
What's the problem?
Just ran into this problem myself today. As far as I understood, it comes from the fact that recently Apple stopped maintaining their version of Java in favor of an official version for the MacOS X from Oracle. The Oracle version, however, doesn't have the same directory structure as before, and the build script generated by Eclipse assumes the old structure.
You can see many bug reports related to this. E.g.,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=371215
https://bugs.eclipse.org/bugs/show_bug.cgi?id=378596
https://bugs.eclipse.org/bugs/show_bug.cgi?id=385077
I heard that switching to using Java 6 would solve the issue, as MacOS X still has the Apple Java 6 installation with the old directory structure. I didn't want to go back to Java 6, so I didn't try this.
Instead, I tried creating the directory that is reported missing (i.e., /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/Classes), with nothing in it. Oddly, it seems to have worked.
Let me know if it works out for you as well... Future updates of Eclipse might also fix this (I updated mine today, but the problem was still there).
This is fixed in Eclipse 3.8.2 and 4.3.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=392434
http://coldfire.riaforge.org/
I can't get the current version (1.9.207.249) to work in with Firefox 14.0.1 with Firebug 1.10.2.
I assume it is broken because the plugin has not been updated for the release of Firebug 1.10.
Has anyone got it working with these settings?
A new version of ColdFire was released that should work with Firefox 15/Firebug 1.10.
https://github.com/nmische/ColdFire/downloads
Based on this I will assume it's still alive. Perhaps try the Chrome version?
http://www.raymondcamden.com/index.cfm/2012/8/24/First-release-of-ColdFire-for-Chrome
I'm unable to run any selenium tests since I updated Firefox to 3.6. Is it happening just to me or is it everybody?
Error message I get is: Could not start Selenium session: Failed to start browser session
This is in Windows Xp.
Ok. Found the problem. My Netbeans was using version 1.0.1 which did not support 3.6.
This fixed it: http://geekswithblogs.net/thomasweller/archive/2010/02/14/making-selenium-1.0.1-work-with-firefox-3.6.aspx
You can also try the extension "Nightly Test Tool" before a extension officially supports a new released version.
Selenium 1.0.3 was updated to work with Firefox 3.6 so suggest updating your version instead of going in and hacking the jar file.
You can get the latest version from http://code.google.com/p/selenium/downloads/list