Comments on: New versions of the Selenium helper

By: Felix Geisendörfer

Felix Geisendörfer — Tue, 23 May 2006 12:44:23 +0000

Ok I’ve tested the new Selenium version together with your new helper and it works great. All I had to do was to remove pause() commands for ajax and replace the next assertText with waitForText – sweet ; ).

Anyway, IE still doesn’t know how to handle XPath’s that look like this:

xpath=id(‘content’)/h1

and rather wants to have them like this:

xpath=//*[@id='content']/h1

So I ported my fix for this to the new version and updated the package with it. This time it’s just adding 2 lines to the __getRow() function instead of modifying tons of other functions ; ).

Again, thanks for doing this great Selenium helper, it’s just the most useful tool for web testing out there ; ), thx for sharing!

–Felix

By: Felix Geisendörfer

Felix Geisendörfer — Tue, 23 May 2006 11:44:36 +0000

cakebaker: Hm, I’ll test that. I’m not sure how xpath are handled. But I think they get proccessed by the browsers themselfs and the problem was not with Selenium but rather with IE. I’ll see ; ).

Btw. I finally integrated Akismet over at thinkingphp.org and it seems to work just great, thx for the tipp ; ).

By: cakebaker

cakebaker — Tue, 23 May 2006 07:19:03 +0000

Well, the reason why your fixes are not in the new helper is that I don’t know if it is still an issue with Selenium 0.7. But it is fine if you release a new version if the fixes are still needed.

By: Felix Geisendörfer

Felix Geisendörfer — Mon, 22 May 2006 20:26:13 +0000

This new Selenium release seems awesome on paper, I’ll test it as soon as I get a chance to.

It also seems like the 3.0 version of the Helper has a lot more features then the old one!

But it seems like you’ve not merged my xpath fixes (or let’s say IE hacks) for 2.0 in it. Is there a specific reason for that or would it be fine if I release a 4.0 and put them back in?

Anyway, thx a lot! Felix