<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Observations from katas</title>
	<atom:link href="http://johannesbrodwall.com/2009/12/23/observations-from-katas/feed/" rel="self" type="application/rss+xml" />
	<link>http://johannesbrodwall.com/2009/12/23/observations-from-katas/</link>
	<description>Johannes Brodwall&#039;s Musings on Software Architecture and Programming</description>
	<lastBuildDate>Thu, 29 Jul 2010 15:37:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Johannes Brodwall</title>
		<link>http://johannesbrodwall.com/2009/12/23/observations-from-katas/comment-page-1/#comment-127640</link>
		<dc:creator>Johannes Brodwall</dc:creator>
		<pubDate>Mon, 22 Feb 2010 19:32:02 +0000</pubDate>
		<guid isPermaLink="false">http://johannesbrodwall.com/?p=497#comment-127640</guid>
		<description>An IDE is allowed, but code generation is not. The first point of the exercise is to really understand what code is needed for a full stack application. The second point is to explore testing at different levels, so you must write tests for both the web, the DAO and the controller.&lt;br&gt;&lt;br&gt;The final point is to get a feeling how long it really takes to get something verifiably working. Before I started practicing, I thought it would take 10 minutes. After I practiced, but before I started timing myself, I though it would take 20 minutes. After I started timing myself, 90 minutes was about right.&lt;br&gt;&lt;br&gt;Code generation isn&#039;t necessarily bad, but the point of the exercise it to explore what code will be generated. You don&#039;t necessarily have to test *everything*, but the point of the exercise is to explore how you would test *anything*.</description>
		<content:encoded><![CDATA[<p>An IDE is allowed, but code generation is not. The first point of the exercise is to really understand what code is needed for a full stack application. The second point is to explore testing at different levels, so you must write tests for both the web, the DAO and the controller.</p>
<p>The final point is to get a feeling how long it really takes to get something verifiably working. Before I started practicing, I thought it would take 10 minutes. After I practiced, but before I started timing myself, I though it would take 20 minutes. After I started timing myself, 90 minutes was about right.</p>
<p>Code generation isn&#39;t necessarily bad, but the point of the exercise it to explore what code will be generated. You don&#39;t necessarily have to test *everything*, but the point of the exercise is to explore how you would test *anything*.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://johannesbrodwall.com/2009/12/23/observations-from-katas/comment-page-1/#comment-127638</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Mon, 22 Feb 2010 17:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://johannesbrodwall.com/?p=497#comment-127638</guid>
		<description>Interesting...&lt;br&gt;So then you must have forgotten one of the following:&lt;br&gt;* no IDE allowed&lt;br&gt;* includes 60 mins for lunch&lt;br&gt;Otherwise I think this can be done in about 10mins.&lt;br&gt;&lt;br&gt;Anyhow: Looking forward to a more detailed definition of kata.</description>
		<content:encoded><![CDATA[<p>Interesting&#8230;<br />So then you must have forgotten one of the following:<br />* no IDE allowed<br />* includes 60 mins for lunch<br />Otherwise I think this can be done in about 10mins.</p>
<p>Anyhow: Looking forward to a more detailed definition of kata.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johannes Brodwall</title>
		<link>http://johannesbrodwall.com/2009/12/23/observations-from-katas/comment-page-1/#comment-127609</link>
		<dc:creator>Johannes Brodwall</dc:creator>
		<pubDate>Fri, 19 Feb 2010 21:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://johannesbrodwall.com/?p=497#comment-127609</guid>
		<description>I haven&#039;t defined it properly (but it&#039;s on my todo list). Here is a brief description:&lt;br&gt;&lt;br&gt;Objective: To test drive a new Java web application that updates and queries a database.&lt;br&gt;&lt;br&gt;Acceptance test: A WebDriver test that accesses the application to insert a &quot;Person&quot; object in the application and then searches for the same person.&lt;br&gt;&lt;br&gt;I start by writing this test, which gives an outside-in approach. However, that means that the test will not pass before I&#039;ve written and got to pass a number of lower-level tests.</description>
		<content:encoded><![CDATA[<p>I haven&#39;t defined it properly (but it&#39;s on my todo list). Here is a brief description:</p>
<p>Objective: To test drive a new Java web application that updates and queries a database.</p>
<p>Acceptance test: A WebDriver test that accesses the application to insert a &#8220;Person&#8221; object in the application and then searches for the same person.</p>
<p>I start by writing this test, which gives an outside-in approach. However, that means that the test will not pass before I&#39;ve written and got to pass a number of lower-level tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://johannesbrodwall.com/2009/12/23/observations-from-katas/comment-page-1/#comment-127584</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Fri, 19 Feb 2010 02:43:17 +0000</pubDate>
		<guid isPermaLink="false">http://johannesbrodwall.com/?p=497#comment-127584</guid>
		<description>Can you please point me to the definition of the Java EE Spike Kata?</description>
		<content:encoded><![CDATA[<p>Can you please point me to the definition of the Java EE Spike Kata?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
