“Yeah, yeah! Eat that banana!” they holler at me.

I roll down the window. “Don’t you wish you had one too?” I call back.

There’s a stunned silence. I guess they didn’t expect me to reply, because for all the swagger in their voices a second ago, them seem to be a little sheepish now, not knowing what to say.

Emboldened, I continue: “Then all three of us could be sittin’ here, eatin’ bananas together!!!”

Now they’re really at a loss for words!

And lo and behold, it’s finally time for another release. Let me tell you, I’ll be glad to get this one out of the way. I’m excited about the improvements and fixes it brings, but doing this stuff alone during one’s free time is … difficult. For a detailed list of changes in this release, please refer to the documentation bundled with the extension. I’m going to highlight the biggest changes:

Firstly, ui0.7 introduces a new rollup Selenium command, which can be used to group multiple individual Selenium commands. It is best used with commands that use ui locators. Rollup rules are written in a simplified javascript notation, and are shareable with the Selenium RC. This is pretty great actually – it means you can record using the IDE, apply the rollup rules to automatically group commands together, then export the test into a driven language and run the test programmatically. Need to update the testcase? No problem – if your testcase can be round-tripped or you kept and HTML version of it, continue to edit – with rollups – using the IDE!

Next, the locator defined for UI elements no longer has to be XPath. All other locator strategies are acceptable now. I made this change after Doug Seller’s comments at GTAC about CSS locators evaluating anywhere between 40-60% faster than XPaths on IE. So now your UI elements can take advantage of that too!

Speaking of XPath performance, the buggy implementation of an XPath uppercasing function in ui0.6 has been retired. Technically, UI-Element no longer needs to uppercase XPaths … but I borrowed from the ajaxslt library and implemented an XPath transformation function anyway, to demonstrate it could be done. I did some research on non-native XPath performance, and found that the case-insensitive “hack” included in Selenium Core to date is degrading performance by roughly 100%. One way to solve this would be to uppercase or lowercase the XPath before evaluation, depending on specific browser requirements (IE needs upper, Safari needs lower). This would allow removal of the hack. I’m planning on creating a Selenium JIRA ticket for this, but for now the function is still being exercised (read: tested!) within UI-Element.

This should be a pretty polished release, compared to the others. I hope you enjoy it! Remember, feedback makes me happy!

I’m consolidating into a single download link:

selenium-ide-0.8.7ui0.7.xpi (or higher)