It looks like the jssh plugin (required to run WatiN) still needs work going by FireFox Bug 586869, to quote:
Probably obvious to anyone who ought
to be trying to maintain jssh, but, to
get it back all you have to do is "hg
up -r 3ca5d6674feb" and copy it to
wherever you're going to work on it.
Haven't found much recent activity on SO for jssh either.
Firefox + jssh build
WatiN - Support for firefox and chrome
check the links - watin works with firefox latest version after installing mozrepl-jsshv2.6.xpi provided by Fabian
Thanks to Fabian. I hope the Watin and Firewatir community embeds this xpi in their repo
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 am not able to run my GWT application due to browser plugin issue. I have tried to find the GWT plugin for Mozilla Firefox browser for the version of 36. Could you please anyone can help me to identify the suitable plugin.
Rationale can be found in the GWT forum: https://groups.google.com/d/msg/google-web-toolkit/QSEjbhhHB4g/wtI5TYFRevsJ
TL;DR: the plugin was using APIs that have been removed in Firefox 27, so it's no longer possible to compile it (and it was required to recompile it for each new version of Firefox).
Now, I am successfully running my gwt application on any of the browser, without installing any browser plugin. If you are using gwt-2.6.0, run your application in Super Server Mode. That will generate a link related to your application. Place that link in any browser url bar and run it. But it will take some time of compiling the application and then you will get the UI on the browser screen. To install gwt-2.6.0 onwards, your installed JDK should be after 7 version.
I had a situation where a user saw an error on her browser which is Firefox. It might be an older version. Is there a way to test multiple versions of Firefox without downloading a bunch of them?
You can use Utili Mozilla Firefox collection if you want to test your site in different versions of Firefox. It's really convenient - a lot of versions in one pack.
http://utilu.com/UtiluMFC/
(I'm not associated with this company)
cheers
I have a folder /browsers with custom versions of browsers, e.g. firefox, chrome, opera.
Then launch the different version when you need to test a specific version rather than launching the default one from your Applications.
*e.g. just rename the installed .app.
Chromium.app rename to e.g. Chromium_19.app need to disable auto-updates
Firefox.app rename to Firefox_38.app
firefox releases
Chrome releases
Opera releases
Multi Safari
Yes you can do this. I have gone through multiple links to find its solution. For example you want to install firefox 4.0 but want to keep 3.6 as well then you need to install Firefox 4.0 using the Custom Installation option, in a uniquely named folder — like /Program Files/Firefox 4.0/ — don't let 4.0 run after the installation procedure is complete.
Create a new profile exclusively for the 4.0 beta version and create a desktop shortcut with -P "profile" appended to the target to launch that profile.
Helpful links will be link1 and link2.
During the search I have also found one software utilu that may be useful, but clearly speaking I have not tried that yet, will try later.
there sites like these http://browsershots.org/. They let you test browsers without downloading.
If you're on OSX using Homebrew, you can install via brew cask:
brew tap goldcaddy77/firefox
brew cask install firefox-46
More info can be found at the git repo homebrew-firefox
I'm trying to install the web developer plugin, and it's failing with a message that "Web Developer 1.1.8 could not be installed because it is not compatible with Firefox 3.6.13".
I don't believe that it's actually incompatible; rather I think the problem is because the installation fails during a validation check, probably because the corp. network is messing with the connections. The message I get is that:
services.addons.mozilla.org uses an invalid security certificate
and when I view the certificate, it's issued by the networking group, not mozilla.
Is there a way to by-pass the version check so I can install it?
The most likely explanation is that the XPI you were trying to install had em:maxVersion in its install.rdf smaller than the Firefox version, so Firefox was checking with addons.mozilla.org to see if the version you were trying to install was marked as compatible (addons.mozilla.org allows to bump the maxVersion, but doesn't update the XPI it serves to the users).
If for any reason that update check failed, Firefox wouldn't let you install the extension.
The solution in that case (extension version actually compatible with Firefox, but has stale information in its install.rdf) would be to edit the XPI to bump maxVersion manually before attempting to install the XPI.
That's weird that it's giving you the "not compatible with Firefox version x" message since, as you say, that doesn't seem to be the actual problem. See if this works: Right-click on the installer link and select "Save Link As..." and save the file on your hard drive. It will be called something like webdeveloper.xpi. Then just drag and drop the file onto Firefox.
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