Comments on: Testing Ext Applications With Selenium

By: neocoder

neocoder — Thu, 05 Mar 2009 03:24:02 +0000

I just wrote an article on how we’ve been testing an ExtJS UI in Java at:

http://www.neocoders.com/portal/articles/selenium-and-extjs

Primarily, it describes how we got around having to assign hand-crafted IDs to all the Ext components and how we synchronise the tests with AJAX.

hope it helps somebody,
Lindsay

By: darrellmeyer

darrellmeyer — Tue, 04 Nov 2008 16:19:42 +0000

Thanks guys for your comments and information, it is very helpful. I think both Selenium and GWT JUnit tests complement each other (unit tests vs. integration tests) and can provide betting testing coverage for when combined.

By: jgw

jgw — Tue, 04 Nov 2008 15:14:50 +0000

Thanks for pointing that out, Thomas. I want to add that in 1.5 you actually can already launch remote tests using selenium (just use the -Dgwt.args=”-selenium host:port/*browser” vm option when launching the test). This makes it a lot easier to test multiple browsers.

I also want to add that while Selenium is great for end-to-end functional tests of your UI, you can use the JUnit framework to test many things more easily, because your Java code usually already has references to the things you want to test (as opposed to having to do lots of XPath tricks).

By: tbroyer

tbroyer — Tue, 04 Nov 2008 14:29:37 +0000

Just a note about the above quoted text from the article (already posted as a comment to the original article on the Ext JS blog): GWT test cases can be run in “web mode” (compiled code) in any browser (eventually several browsers simultaneously, and eventually using Selenium RC to launch the browsers); though GWT/JUnit integration is all about unit-testing, not UI-testing.