Comments on: Testing Ext JS & Ext GWT Applications With Selenium

By: shr1975

shr1975 — Thu, 11 Mar 2010 08:59:35 +0000

SAHI is a web application test automation tool. It is on similar lines as Selenium, but I found it to be much better as compared to Selenium in that it takes care of the random, unique ids.

When working with Selenium, what I experienced was that it did not work with menus(the sub-menus were not being shown as the mouseOver was not being trapped) and context-menus. That was a big negative point for us.

We found SAHI much better than Selenium on these counts; we were able to record the steps right from logging in, to opening a particular screen through the menu, to entering different oombinations of data, to saving them and finally re-opening the screen all without a hitch.

Here’s the URL:
http://sahi.co.in/w/sahi

By: HID Kit

HID Kit — Wed, 10 Mar 2010 13:00:11 +0000

Thanks very good post and no doubt this is the best blog.

By: sagsagar

sagsagar — Wed, 10 Feb 2010 11:39:53 +0000

How extjs objetcs catch in qtp or any automation testing tool?

By: lida

lida — Sun, 24 Jan 2010 12:17:58 +0000

n to take advantage of more of the ssnative ddfunctsddascc

By: kapadokya

kapadokya — Fri, 22 Jan 2010 14:17:53 +0000

Currently ExtJS generates unique but meaningless id’s on DOM elements. By default, Selenium IDE uses these id’s when auto recording events on HTML control elements (buttons, fields etc). Add a new widget on the page and the test script recordings all break.

Some time ago I proposed that ExtJS support an additional config property on all widgets so that a meaningful prefix can be applied to all HTML control DOM elements that are generated by the widget. Generated ids would then be stable and meaningful so that recorded tested are readable and maintainable. Yes, you can painfully rewrite each recorded rule to use an xpath or CSS selector but this costs valuable time. It would be so much simpler and quicker to use Selenium if it’s recorded coded that uses ids *just worked*.

By: Ben 10 Mania İzle

Ben 10 Mania İzle — Thu, 14 Jan 2010 15:20:10 +0000

Usefull article.
Thanks.

By: Red56

Red56 — Thu, 22 Oct 2009 18:19:10 +0000

Get out of your kids way, relax, let them be kids and watch them grow & flourish. ,

By: Shruti

Shruti — Mon, 21 Sep 2009 10:09:25 +0000

Hi,

Please let me know if there is a solution to the problem of dynamic ids in a GWT ext application ? How can they be handled .

thanks,
Shruti

By: LiR

LiR — Fri, 18 Sep 2009 21:37:58 +0000

Instead of using
“//input[@name='company']“
you can also use locator
“company”

By: Fredrik Wendt

Fredrik Wendt — Mon, 07 Sep 2009 11:50:18 +0000

Hi. Interesting to blog about the worst part of Ext JS – because it is.
This blog post is almost one year old. Papers were submitted to the Ext JS conference in April – zero (0) topics touched on automated testing (with Selenium). There’s no doubt that Ext JS is the strongest competitor when developing large (huge) Ajax applications.

The team I’m at have written ~25000 lines of JavaScript code. The full GUI consists of one HTML page and the rest is a close to traditional desktop client application. We’ve extensively used Selenium to drive “acceptance” test and for the most part wrote small wrapper classes around Ext base classes like Button, Menu, MenuItem etc making minor modifications to the templates in order to use ID:s that doesn’t change as soon as the design guys makes up their mind (again and again). (xpath is just too slow in IE to be used in real projects with hundreds of test cases, unless you’re fine with running test suites once a day and hiring monkeys to manually click the “This script is too slow” dialog …)

I really hope that the Ext developers stopped ignoring this issue and not only focused on making the best framework available, but also the one being most testable.