I wanted to work some more on the comments for translations, including writing automated cucumber tests for everything. It turned out that tests that need Javascript don't work anymore. The Javascript tests are set up with Selenium which launches a real browser, in my case Firefox. The launching part still worked, but somehow Selenium couldn't communicate with FF so that the empty FF window just sat there and nothing happened.
It's been a while since I last run the Javascript tests, but my updated version of Firefox (or actually Iceweasel, which is Debian's variant of FF) seemed the most likely culprit. I updated Selenium, but that broke everything at first. After a few iterations of googling error messages, updating more of the test setup, googling new error messages, tweaking configuration files etc I'm now at a point where all the tests work again--except for the Javascript ones.
Now I'm seriously stumped. Selenium launches Firefox and I can watch the test steps unfold, so that's better than before--it's just that the tests run into the non-Javascript parts of the application and I have no idea why. Clicking through the preferences of the FF launched by Selenium shows that Javascript is enabled. WTF?
Somehow I was expecting more to come out of a mostly free sunday spent coding.
This entry was originally posted at
http://rebecca2525.dreamwidth.org/5748.html. Please comment there using OpenID.