sebastianbergmann/phpunit-selenium — Issue #68: Selenium behavioral difference between PHPUnit Selenium vs other Selenium RC bindings?
Author: daluu
Created: 2011-11-06 01:46:43+00:00
State: open

You can either say this is an issue/bug w/ PHPUnit Selenium extension, or bug with Selenium RC itself so be more of a discussion item. Bringing this up due to comment in my post here:

http://groups.google.com/group/selenium-users/browse_thread/thread/16d0ab7cd488f7e3/f974dac3ae72ed15#f974dac3ae72ed15

Excerpt from that thread:

Me:
I know there are differences in Selenium behavior between browsers and OSes. But was wondering if anyone has noticed issues with Selenium RC across language bindings (that is using same test flow, same locators, but different languages). I just recently noticed case where locator and thus test worked with Python binding but failed in PHPUnit / PHP binding for same exact locator. But I guess this is less noticeable as few people switch language bindings for a test in Selenium.

Response I got so far:
That can't happen, unless PHPUnit itself is messing with things (PHP is not a language supported by the Selenium Project). All the language bindings merely pass the command and arguments to the server, which either executes them itself or passes them to the JavaScript code in the browser, where most of the commands are actually performed. The client-side (binding) code doesn't really do anything except talk to the server.

So I wanted Sebastian's (and team's) take on this. Unfortunately, the problematic locator is for a non-public site/app that I can't share. Wish I can find a particular locator on public site that can reproduce this issue. What I can say is that the problematic locator was a select element and we are trying to both read and set its values (some option element within).