I'm having kind of a big problem that I need to solve pretty quickly, but I'm just not sure how.
Right now I've got an app that's stuck using the selenium-webdriver gem at v0.1.4. I'm using Ubuntu 10.10 and the Firefox Stable PPA. A few nights ago, Firefox forced their new v5.0, and now the Webdriver extension in Firefox is broken. That basically means that when I run Cucumber tests, Firefox will launch, but it won't be able to do anything, since the Webdriver is disabled.
Now, I've been watching for days, and it looks like the folks over at Selenium have updated their 0.2.x release to be compatible with Firefox 5. But I'm hesitant to upgrade what appears to be a significant version increase. I've tried downloading Firefox-4.0 from the FF website, but from what I can tell they just sneak it in as FF5 (every time I launch FF4 directly, it still launches FF5). I've also tried to use the Force Version feature in Synaptic, but FF4 isn't available there either.
I either need to find a hack to fix webdriver 0.1.4 or downgrade to FF4. Does anyone have any advice?
====================================
Edit: Some of the above was written in frustration amid a number of dependency issues, and a lot of it was from my own misunderstanding. I meant no offense, and am kicking myself for not seeing was staring me right in the face. I've toned down my rant. Selenium and Firefox are solid products, and I'm just glad I got them working again.
Solved the problem by just upgrading to >= 0.2.2. I thought the version jump from 0.1.x to 0.2.x indicated potential compatibility issues that I wasn't prepared to deal with at the time.
There's a post here by a user named jarra that appears to have directions for installing FF4 back to the mac and then forcing selenium to use FF4.
Do you mean that the extension was disabled due to incompatibility?
Then you can force compatibility by adding the entry extensions.checkcompatibility.5.0 to about:config, with value false. Restart Firefox. If the addon remains disabled, install MR Tech's Toolkit addon, restart Firefox, right-click on the addon, "enable incompatible addon" (or something else). After restarting, Webdriver should work fine.
Related
I installed Paros. At first, it worked fine. However, from the second start, Paros will start and automatically turn off after a few seconds. I also tried to reinstall but the installer will automatically turn off. Why is that?
Window 10 64bit
I install 32bit java.
Any particular reason for using Paros? Its not been updated for over 10 years.
You'll be much better off using OWASP ZAP, which was forked from Paros in 2010, is free, open source and is very actively maintained: https://github.com/zaproxy/zaproxy/
I've recently began to work with Ranorex and already got Firefox and Chrome working. Internet Explorer only seems to track dom elements for me. I don't get the usual elements I get in other browsers thus I can't track or run any tests.
I've already tried to reinstall ranorex, restart the computer, trying to deactivate security-features in IE and setting a few different ranorex settings.
I've tried ranorex 6.1 and 6.2.0 and for Internet explorer I am using the most recent version. Windows 7 64 bit.
I would love to hear any suggestions which I could still try to get it to run.
Thank you,
Christopher
Have you tried to turn off the Protected mode and the enhanced protected mode?
I packaged my addon and tested in firefox 31 , it worked fine.
I try to install it on firefox 21 , I got an error mentioning invalid package addon/sdk/window
my question is how could i include packages so that it could work on firefox 21?
Any ideas?
Thanks
I dont think that will be supported, as firefox is improving day by day, and changes in the version of SDKs also.
Also, the firefox v21, must not be supporting the SDK packed addons. You should create them using XUL.
cfx has the option --force-use-bundled-sdk to bundle the sdk libraries themselves with the XPI, but that doesn't guarantee that those modules will work in older firefox versions
You could also wrap the module require() in try-catch blocks and use older APIs on failure. I think some modules were renamed over time
Also, FF21 is long out of support. At the time of writing 31.4.0esr is the oldest still maintained release.
Background info:
Over the past week, I have been messing around with Chrome extensions and had no problem creating my extension. Great, Chrome rocks for making the development process very easy to learn, and, well... just easy!
Now I have it in my mind that I'd like to create this extension for as many browsers as I can, so I decided on Firefox next.
What a mess! There documentation has done nothing but give me a headache and waste my time so far, VERY convoluted and just generally unorganized.
I have managed to locate a code sample for a simple extension that I think I can use as a starting point and have begun messing around with - fine...
I have learned that this sample extension will not work with anything less than Firefox 4, as it uses the bootstrap technique to make the extension installable without a browser restart. Ughhhhhh....
Now we arrive at my questions:
Is it possible to develop an extension for Firefox 7 that will work with previous versions of Firefox? I don't even care about anything prior to Firefox 4, if that's the cutoff point for restart-less installations. It would be nice to know that what I am spending all this time making will work consistently and for more than a week when the user is prompted to upgrade next.
How about the reverse? Can I create an extension that is compatible with Firefox 3.5 through Firefox 7? I realize it would require a restart to install, but that would be acceptable if it resulted in a working extension regardless of the version.
Can anyone with experience on this stuff share a bit of what I'm getting myself into here? It seems like this is a nightmare of a platform to develop on, and that I will be constantly fixing my extension.
One last piece of relevant information:
The extension I am developing is purely javascript based - this stuff should work (I think?) because it's dependent on just one feature "content scripts" that really shouldn't be changing in implementation between versions at this point... right?
So what exactly am I missing? How do you create easily manageable Firefox extensions that will work in all versions of the browser?
Thanks everyone! :)
You have to distinguish between "traditional" extensions and extensions built with the Add-on SDK. The former are far more powerful given that they have direct access to all APIs the browser uses - but that's also the reason why they are more complicated to write and why the documentation is rather unordered (there are simply very many things that you could do, far more than you could with Chrome). They are also more likely to break as the browser changes. The Add-on SDK on the other hand gives you a limited API much like Chrome. The Add-on SDK currently supports everything from Firefox 4 onwards (yes, because of restartless installation), with the promise that browser changes will merely require your add-on to be recompiled with a newer version of the Add-on SDK. In fact, that recompiling will likely happen automatically in future for add-ons hosted on addons.mozilla.org. On to your questions:
Is it possible to develop an extension for Firefox 7 that will work with previous versions of Firefox?
Sure it is. The Add-on SDK currently marks your add-on as compatible with anything between Firefox 4 Beta 7 and Firefox 8 Alpha 1. Even as traditional add-ons go - starting with Firefox 4 the differences between particular browser versions are rather small, most things work in all of them. You can also stay compatible with Firefox 3.x but depending on what you do it might require some effort. Important information:
Firefox 4 for developers
Firefox 5 for developers
Firefox 6 for developers
Firefox 7 for developers
How about the reverse? Can I create an extension that is compatible with Firefox 3.5 through Firefox 7?
It doesn't matter which way you go. I wouldn't recommend spending much time on Firefox 3.x support however. With Firefox 3.5 no longer supported the only relevant version is Firefox 3.6. According to the statistics of my add-ons roughly 18% of the Firefox users continue using it. In the next few months this percentage will get significantly smaller, especially when Mozilla announces end-of-life for this branch. So for a new add-on supporting it is usually not justified.
Can anyone with experience on this stuff share a bit of what I'm getting myself into here?
Depends on how complicated your add-on will be. Given that you are developing an equivalent to a Chrome extension, you will most likely be using the Add-on SDK which means that there won't be any compatibility problems. As traditional add-ons go, simple add-ons that don't rely on some obscure implementation details also typically don't have any trouble staying compatible (I have two add-ons that didn't need a single adjustment since Firefox 3.5). Add-ons that go deep down into the system are more problematic of course.
I'm developing an application on two different machines (home and work) and while the home one seems to run just fine, the work one is, for lack of a better word, possessed. It has been exhibiting the following issues:
When loading the application, it will start at the simulator's main screen instead of starting the application at random intervals. You can start the application and have it work fine, then close the simulator, reload, and have the same codebase not load.
Going to applications doesn't show the application itself, in fact it never does.
Trying to load the applications cod file (File->load java program) never works. Tried the steps in this thread, with unreliable results.
Extremely small changes, such as modifying the value of a width variable by one, commenting out a function such as makeMenu or adding a button will cause code to no longer work, with no errors shown by the IDE.
Using clear.bat with sometimes work, sometimes not. Same with manually removing all files with the name of the project.
reinstalling the eclipse environment and the blackberry plugin did nothing more then burn off an hour.
having "load on startup" in the blackberry_app_descriptor.xml file is set.
Both systems are using Eclipse 3.5.1, BB plugin for eclipse 1.1 beta, Java 4.5 with the 8300 simulator. THe only difference that I am seeing is the operating system between the two systems. The work one being XP Sp3, home being vista. THe vista one isn't perfect, but I can test variable changes without flipping a coin to see if the app will even load or not.
I've tried the solutions that were similar on this forum, such as this one, but it looked to be that those solutions are dated as none of the options for the steps existed in my eclipse install.
So has anyone ran into such baffling behavior, and can it be fixed? Anything that I might have missed that could be tried?
I've been seeing this behavior with the new 1.1 plugin, the application doesn't load on startup and the FIle->load java program doesn't help. For me, the solution was I have to run a clean build every time, that is the eclipse clean and build instead of just build, not the clean.bat... Hope this helps!
Try clearing resources that have improper naming structure in your projects stuff with spaces or special character in the name of the file.
It took me two days to figure out.
One solution i got regarding your problem.
As I See Please run the application first time as Run as blackberry simulator
that is got start and here pick up run and then Run as Blackberry simulator