I recently spent a bit of time making our Selenium tests play nicely with Firefox 3 and spent quite a lot of time starting at
1
| |
Selenium would launch Firefox, and then Firefox would just sit there doing nothing. Eventually some digging around found a ticket on the Selenium issue tracker. It turns out Selenium installs a tiny little extension into the Firefox profiles it generates that basically just lets selenium kill firefox by telling it to go to a magic chrome url. Firefox extensions specify which versions they are compatible with and the one embedded in selenium had 2.0.0.* as their maximum version (and this is still the case with the latest downloadable release (although you could of course download the nightly builds)).
It seems that this was the only thing from keeping selenium and Firefox 3 playing nicely together as changing the maximum version to 3.0.* got all our tests passing again with our existing version of selenium (0.9.2).
All I had to do was extract the relevant files from selenium-server.jar:
1 2 3 4 5 6 7 8 9 10 | |
This extracts the files (and the directory structure containing them). To be honest I’m not entirely sure of the difference between all of these extensions - safest bet seems to be changing them all. Now edit all of the .rdf files (they’re just text files) and change the maximum version from 2.0.0. to whatever you want (for example 3.0.) and put them back in the jar:
1 2 3 4 5 6 7 8 9 10 | |
Voila! all done