<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Test driven development for GWT UI code</title>
	<link>http://robvanmaris.jteam.nl/2008/03/09/test-driven-development-for-gwt-ui-code/</link>
	<description>Rob van Maris' blog about hard stuff made simple</description>
	<pubDate>Mon, 15 Mar 2010 11:47:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3</generator>
		<item>
		<title>By: Daniel Wellman</title>
		<link>http://robvanmaris.jteam.nl/2008/03/09/test-driven-development-for-gwt-ui-code/#comment-47</link>
		<dc:creator>Daniel Wellman</dc:creator>
		<pubDate>Thu, 13 Mar 2008 02:26:25 +0000</pubDate>
		<guid>http://robvanmaris.jteam.nl/2008/03/09/test-driven-development-for-gwt-ui-code/#comment-47</guid>
		<description>Very nicely written.  We did the same thing with our GWT project.  We did write some GWTTestCases for a) any widgets that needed to correctly map fields from a model object and b) for JSON parsing code which required native Javascript (JSNI).  They were very slow, but we separated them into their own build step.  This way we ran all the fast unit tests frequently while developing but the continuous integration server would run both the fast and the slow tests.</description>
		<content:encoded><![CDATA[<p>Very nicely written.  We did the same thing with our GWT project.  We did write some GWTTestCases for a) any widgets that needed to correctly map fields from a model object and b) for JSON parsing code which required native Javascript (JSNI).  They were very slow, but we separated them into their own build step.  This way we ran all the fast unit tests frequently while developing but the continuous integration server would run both the fast and the slow tests.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
