21goto wrote:Anyone have any success testing a SmartGWT application with Webdriver?
Smart GWT makes it difficult by giving you no control over the IDs of the page elements. For even more fun, it renders things differently for different browsers, so even your horrendous xpath expressions which work on Firefox won't work on IE.
Hmm...this is the eValid forum, not the WebDriver forum, but in any case we'll try to answer.
The big issue with SmartGWT, as well as with GWT itself, is that the ID tags change names every time the application is updated.
For recorded from life scripts this plays havoc because if things move around then even eValid's adaptive playback feature gets confused. Whoever would have thought that it was OK to reassign all the ID tags? Anyway, we can observe that it is strange to do that but as the tester we can't complain (and we certainly can't get it fixed!).
But there is a way around the dependes on constand ID tags and that is to convert the script into one that uses the "structural commands" (the index/motion commands) only. While these eValid commands don't have adaptive playback you really don't need that feature because a structural command sequence will work on the layout of the page in a logical sense.
We've found that such sequences are VERY durable.
The eValid Team
