<?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: Adding a swing component to a Form Test Driven</title>
	<atom:link href="http://www.rojotek.com/blog/2004/09/22/adding-a-swing-component-to-a-form-test-driven/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rojotek.com/blog/2004/09/22/adding-a-swing-component-to-a-form-test-driven/</link>
	<description>Software Development in Brisbane</description>
	<lastBuildDate>Fri, 03 Feb 2012 20:00:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: ana theeson</title>
		<link>http://www.rojotek.com/blog/2004/09/22/adding-a-swing-component-to-a-form-test-driven/comment-page-1/#comment-550</link>
		<dc:creator>ana theeson</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-550</guid>
		<description>Sorry, but thats the worst misuse of unit testing I have ever seen. When testing a UI you need to test the function of the form, not the construction. 

This is like having a class with a private field that you set to 6 through a constructor. You do not need to do assertEquals(myfield, 6), this is un-necessary testing.

How long does it take to just view the form (JDemo or others) compared to creating your unit test for it? In my opinion its a complete waste of time testing that you add something AFTER you add it...?

There are a time and place for unit tests. Usually the best place to test forms is by simulating user input (java.awt.Robot) then testing to see if the MODEL behind the form is responding correctly.

 
</description>
		<content:encoded><![CDATA[<p>Sorry, but thats the worst misuse of unit testing I have ever seen. When testing a UI you need to test the function of the form, not the construction. </p>
<p>This is like having a class with a private field that you set to 6 through a constructor. You do not need to do assertEquals(myfield, 6), this is un-necessary testing.</p>
<p>How long does it take to just view the form (JDemo or others) compared to creating your unit test for it? In my opinion its a complete waste of time testing that you add something AFTER you add it&#8230;?</p>
<p>There are a time and place for unit tests. Usually the best place to test forms is by simulating user input (java.awt.Robot) then testing to see if the MODEL behind the form is responding correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://www.rojotek.com/blog/2004/09/22/adding-a-swing-component-to-a-form-test-driven/comment-page-1/#comment-551</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-551</guid>
		<description>To each their own.  I am very happy with the approach.  

Perhaps I didn&#039;t make it clear that each of those steps is preformed before the components are added to the form.  It is the application of approaches described in books like Kent Beck&#039;s Test Driven Development.

I agree that having the tests to support the view/model interaction is important as well, and will be doing that.  The idea of being able to have a series of tests that checks that the components are on the screen is important, because this is a seperate concern to the hooking up of the components to the model.

That is the motivation for the tests.</description>
		<content:encoded><![CDATA[<p>To each their own.  I am very happy with the approach.  </p>
<p>Perhaps I didn&#8217;t make it clear that each of those steps is preformed before the components are added to the form.  It is the application of approaches described in books like Kent Beck&#8217;s Test Driven Development.</p>
<p>I agree that having the tests to support the view/model interaction is important as well, and will be doing that.  The idea of being able to have a series of tests that checks that the components are on the screen is important, because this is a seperate concern to the hooking up of the components to the model.</p>
<p>That is the motivation for the tests.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

