<?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"
	>
<channel>
	<title>Comments on: 3 steps to creating a GWT JUnit test</title>
	<atom:link href="http://thediscoblog.com/2007/04/27/3-steps-to-creating-a-gwt-junit-test/feed/" rel="self" type="application/rss+xml" />
	<link>http://thediscoblog.com/2007/04/27/3-steps-to-creating-a-gwt-junit-test/</link>
	<description>Can you dig it man?</description>
	<pubDate>Sat, 22 Nov 2008 04:20:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: The Disco Blog &#187; Blog Archive &#187; 3 steps to running GWT JUnit tests in Eclipse</title>
		<link>http://thediscoblog.com/2007/04/27/3-steps-to-creating-a-gwt-junit-test/#comment-9873</link>
		<dc:creator>The Disco Blog &#187; Blog Archive &#187; 3 steps to running GWT JUnit tests in Eclipse</dc:creator>
		<pubDate>Sat, 28 Apr 2007 18:58:57 +0000</pubDate>
		<guid isPermaLink="false">http://thediscoblog.com/2007/04/27/3-steps-to-creating-a-gwt-junit-test/#comment-9873</guid>
		<description>[...] 3 steps to running GWT JUnit tests in Eclipse  One of the hippest things about Google&#8217;s Web Toolkit is that you can write JUnit tests that can verify asynchronous server side behaviors. What&#8217;s more, your copasetic JUnit tests can also be run via Eclipse (not to mention a build process like Ant, etc), which has the effect of decreasing the time between when you code a feature and when you can verify it actually works as expected. [...]</description>
		<content:encoded><![CDATA[<p>[...] 3 steps to running GWT JUnit tests in Eclipse  One of the hippest things about Google&#8217;s Web Toolkit is that you can write JUnit tests that can verify asynchronous server side behaviors. What&#8217;s more, your copasetic JUnit tests can also be run via Eclipse (not to mention a build process like Ant, etc), which has the effect of decreasing the time between when you code a feature and when you can verify it actually works as expected. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
