<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Testing Ext JS &amp; Ext GWT Applications With Selenium</title>
	<atom:link href="http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/</link>
	<description>JavaScript UI Component Library</description>
	<lastBuildDate>Sat, 21 Nov 2009 23:37:38 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Red56</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-77458</link>
		<dc:creator>Red56</dc:creator>
		<pubDate>Thu, 22 Oct 2009 18:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-77458</guid>
		<description>Get out of your kids way, relax, let them be kids and watch them grow &amp; flourish. ,</description>
		<content:encoded><![CDATA[<p>Get out of your kids way, relax, let them be kids and watch them grow &amp; flourish. ,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shruti</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-75096</link>
		<dc:creator>Shruti</dc:creator>
		<pubDate>Mon, 21 Sep 2009 10:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-75096</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>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 .</p>
<p>thanks,<br />
Shruti</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: LiR</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-74936</link>
		<dc:creator>LiR</dc:creator>
		<pubDate>Fri, 18 Sep 2009 21:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-74936</guid>
		<description>Instead of using 
&quot;//input[@name=&#039;company&#039;]&quot;
you can also use locator
&quot;company&quot;</description>
		<content:encoded><![CDATA[<p>Instead of using<br />
&#8220;//input[@name='company']&#8220;<br />
you can also use locator<br />
&#8220;company&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik Wendt</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-74284</link>
		<dc:creator>Fredrik Wendt</dc:creator>
		<pubDate>Mon, 07 Sep 2009 11:50:18 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-74284</guid>
		<description>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&#039;s no doubt that Ext JS is the strongest competitor when developing large (huge) Ajax applications.

The team I&#039;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&#039;ve extensively used Selenium to drive &quot;acceptance&quot; 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&#039;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&#039;re fine with running test suites once a day and hiring monkeys to manually click the &quot;This script is too slow&quot; 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.</description>
		<content:encoded><![CDATA[<p>Hi. Interesting to blog about the worst part of Ext JS &#8211; because it is.<br />
This blog post is almost one year old. Papers were submitted to the Ext JS conference in April &#8211; zero (0) topics touched on automated testing (with Selenium). There&#8217;s no doubt that Ext JS is the strongest competitor when developing large (huge) Ajax applications.</p>
<p>The team I&#8217;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&#8217;ve extensively used Selenium to drive &#8220;acceptance&#8221; 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&#8217;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&#8217;re fine with running test suites once a day and hiring monkeys to manually click the &#8220;This script is too slow&#8221; dialog &#8230;)</p>
<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gabriel</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-74117</link>
		<dc:creator>Gabriel</dc:creator>
		<pubDate>Fri, 04 Sep 2009 16:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-74117</guid>
		<description>Don&#039;t waste your time, selenium is no compatible with ext-gwt</description>
		<content:encoded><![CDATA[<p>Don&#8217;t waste your time, selenium is no compatible with ext-gwt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajini</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-72580</link>
		<dc:creator>Rajini</dc:creator>
		<pubDate>Thu, 13 Aug 2009 09:26:27 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-72580</guid>
		<description>Hi,
I&#039;m started learning selenium please reffer some best site where I could get java support code not javascript to practice selenium

Thanks
Rajini</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I&#8217;m started learning selenium please reffer some best site where I could get java support code not javascript to practice selenium</p>
<p>Thanks<br />
Rajini</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-71498</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Fri, 24 Jul 2009 10:52:38 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-71498</guid>
		<description>Nice article.

Tried the test and selecting combo box items doesn&#039;t work. Plus it seems that the provided Java code is outdated.

I have the same sentiments as &quot;wasting time.&quot; For some cases, it&#039;s extremely difficult to test GXT using Selenium. Context Menu does not appear with contextMenu/At; can&#039;t select combo box items using click/At; etc. I hope you can come up with an article discussing these issues and suggesting good workarounds. Right now, writing tests for these cases is a lot of trouble.</description>
		<content:encoded><![CDATA[<p>Nice article.</p>
<p>Tried the test and selecting combo box items doesn&#8217;t work. Plus it seems that the provided Java code is outdated.</p>
<p>I have the same sentiments as &#8220;wasting time.&#8221; For some cases, it&#8217;s extremely difficult to test GXT using Selenium. Context Menu does not appear with contextMenu/At; can&#8217;t select combo box items using click/At; etc. I hope you can come up with an article discussing these issues and suggesting good workarounds. Right now, writing tests for these cases is a lot of trouble.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cinsellik</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-71060</link>
		<dc:creator>cinsellik</dc:creator>
		<pubDate>Sat, 18 Jul 2009 13:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-71060</guid>
		<description>I am grateful to you for this great content.</description>
		<content:encoded><![CDATA[<p>I am grateful to you for this great content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wasting time</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-70961</link>
		<dc:creator>wasting time</dc:creator>
		<pubDate>Thu, 16 Jul 2009 16:36:13 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-70961</guid>
		<description>This little article is great and all, but it didnt save me from wasting tons  of time trying to set up selenium tests for things like grids.  Or for things like combo boxes or filtering or paging.  Seems to be some fundamental underlying EXTJS stuff that makes certain selenium tests almost impossible to write.  I think this is the first serious downside for EXTJS that I have come across.  As of now, I will waste a lot of time fooling with selenium tests for extjs.  And due to the crazy workarounds you have to put in place, the tests are now really brittle.  So that means more wasted in the near future.</description>
		<content:encoded><![CDATA[<p>This little article is great and all, but it didnt save me from wasting tons  of time trying to set up selenium tests for things like grids.  Or for things like combo boxes or filtering or paging.  Seems to be some fundamental underlying EXTJS stuff that makes certain selenium tests almost impossible to write.  I think this is the first serious downside for EXTJS that I have come across.  As of now, I will waste a lot of time fooling with selenium tests for extjs.  And due to the crazy workarounds you have to put in place, the tests are now really brittle.  So that means more wasted in the near future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kabin</title>
		<link>http://www.extjs.com/blog/2008/11/03/testing-ext-js-ext-gwt-applications-with-selenium/comment-page-2/#comment-69592</link>
		<dc:creator>kabin</dc:creator>
		<pubDate>Sat, 27 Jun 2009 09:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://extjs.com/blog/?p=82#comment-69592</guid>
		<description>thank you very nices. ok :d</description>
		<content:encoded><![CDATA[<p>thank you very nices. ok :d</p>
]]></content:encoded>
	</item>
</channel>
</rss>
